Web

Last week a checkout button stopped responding in production. The handler existed, but my script ran before the button did. I moved the setup into DOMContentLoaded and the bug disappeared. The very next day I needed the exact pixel height of a hero image to place a canvas overlay. DOMContentLoaded fired too early and the […]

Last winter I shipped a small redesign that looked flawless in Chrome and Firefox. The first support ticket came from an iPhone, and the frosted header I loved was a flat gray block. The cause was not layout or JavaScript; it was a single missing vendor prefix for backdrop-filter. That one dash decided whether Safari

Last year I reviewed a subscription checkout page that looked perfect in Figma and totally wrong in the browser. The culprit was a single margin-top on a heading that collapsed with its parent and pushed the entire hero block down. That one line reminded me that vertical spacing is not a "set it and forget

Last month I reviewed a retail site where the top nav looked simple, yet pressing Tab jumped from Logo to Help, then into the footer, then back to the menu. The culprit was a handful of tabindex values added years ago to fix a layout change. Keyboard users were forced to play guess-the-next-link, and the

Late at night, I open a dashboard and the white background feels like a flashlight. That moment is why I add theme toggles to almost every product I ship. People read in bright offices, on dim trains, or in dark bedrooms, and they expect the interface to adapt. A tiny slider is a clear signal:

Most teams I work with can build a UI that looks right, yet the moment a panel appears it feels off. It arrives too fast, or stops too sharply, and suddenly the interface feels brittle. That gap between static layout and living motion is where tweening lives. Tweening is the practice of letting the browser

Every time I build a media carousel for a portfolio or a product page, someone eventually asks why the pagination dots drift to the side when the list gets long. The answer is simple: most libraries render the dot list as a long row that stays anchored to the left, so the active dot walks

Last quarter I had to ship a reporting view for a legacy ERP that only emitted XML. The business wanted a clean HTML table, and they wanted it yesterday. I reached for XSLT because it still provides the most dependable way to reshape XML into markup without writing a custom parser. The hardest part wasn‘t

Last month I reviewed a production bug where a checkout button stopped working on first paint. The handler was wired before the DOM existed, so it silently failed. A week later, another team measured hero image size on DOMContentLoaded and got zero, which cascaded into layout math that shifted the page. These two problems share

Last year I shipped a payment page that showed € instead of €. The bug was not in my pricing logic; it was in how the page interpreted bytes. A single missing charset declaration turned perfectly valid data into nonsense for a subset of users. That is the kind of bug that slips through tests

Most teams I mentor can build a page that looks fine in a browser, yet the code underneath tells no story. I still see div-only layouts where the heading hierarchy is broken, the navigation is hidden from screen readers, and a simple layout change requires a CSS pileup. The user experience degrades quietly: search engines

Last month I shipped a marketing page with a soft glassy header. On my Mac, the blur was perfect. Then a support ticket arrived from Windows testers: the header looked flat and washed out. The CSS was valid, but the feature was still gated behind a vendor prefix in one browser and unsupported in another.