Patterns for building software that handles money.

Native elements carry behaviour, accessibility, form semantics, keyboard support, and platform adaptation before styling begins.

The market is repricing software engineering labor—collapsing the premium for generalists while raising the value of deep expertise.

I kept an old iMac alive for years just to run Freehand MX. Halftones, moirés, film separations.

How prioritizing standard HTML features reduces maintenance and enhances long-term interface stability.

How shifting engineering to intent management accelerates feature deployment.

How AI is absorbing the visible friction that open-source communities have always relied on to see—and welcome—newcomers.

Vibe coding is useful for discovery, but software engineering starts when generated code has to be reviewed, owned, operated, and safely changed.

Coding agents made software cheap to build. That just exposed the bottleneck that was always there: deciding what to build.

How the Single Responsibility Principle (SRP) is often misinterpreted and how to apply it correctly to avoid overengineering and underengineering.

Pixel-perfect skeleton loading screens auto-extracted from your real DOM. Zero configuration, zero layout shift.

A platform-agnostic, full specification of the technical features a good website should have. Built in the open under an MIT license.

You don’t really need to be good at prompting anymore. The thing to get good at is the loop that does the prompting for you.

How Dropbox is moving towards agentic systems that can execute scoped tasks, and how we’re building platforms to support those workflows.

About 10 years ago, I realized all the best programmers I had worked with had something in common: they were fast.

The MCPs that make Claude Code useful for iOS, and a working app on your phone by the end of the afternoon.

How to minimize custom prompting and rely on upstream tool updates.

Interactive config generator for Claude Code environment flags. Find your preferred balance of cost, tokens, and thinking.

Why predictable CSS state resolution matters, and how Tasty approaches it with state maps and non-overlapping selectors.

It still hits like a ton of bricks to see the steep decline in Stack Overflow questions. What does that mean about learning in our industry?