You appear to be offline, some content may be unavailable.
On a recent project I finally found a solution to an issue I've run into several times: When listening for events in JavaScript, how can I tell whether an event was triggered directly by a user or by my code?
The single best feature of Vite, as far as I’m concerned, is its simplicity. Compared to the nightmare of configuring WebPack and Babel? Vite is delightfully easy to use.
Hand-code an SVG snowflake, experiment in an interactive playground, and generate infinite random snowflakes with a dash of JavaScript.
Components are everywhere, but they are rarely reusable across systems. A design system component is written differently than a CMS editor component. But does it have to be this way? Could we take one set of components and port them to multiple JavaScript frameworks, import them into design tools, and use them for the editing interfaces in content management systems?
On a recent client project, we built a form that submitted to a third-party registration service. Easy-peasy, right? What followed was a comical series of incidents that served as an excellent lesson in defensive API handling.
Turning simple shapes into complex illustrations using some SVG magic.
Using JavaScript, SVGs, and CSS to procedurally generate unique solar systems.
By leveraging native browser controls, we can make accessible and high-performing components with just a dash of JavaScript.
You may have heard that you should be “linting” your code. What does that mean? Why would you want to do it?
Join me in exploring a recent experience where I started with flawed logic (without realizing it) and the steps I took to fix my bug. Let’s experience some broken code together. 🎉