The growing gap between the code your team ships and the code your team understands. It’s not technical debt. It’s worse.

A giant leap towards outcomes-based billing.

Removing the context-gathering bottleneck for most support work.

How pressure to deliver fast erodes the deep thinking necessary for truly functional products.

Apparently writing code is cheap now. So since the barrier to producing code is gone, the intent behind the code is the most important bit.

AI agents didn’t make the SDLC faster. They killed it. All that’s left is context.

Hot takes and cold truths on software, startups, and the lies we tell ourselves.

If you’ve been anywhere near tech Twitter in the last few weeks, you’ve heard it: SaaS is dead. Everyone has an explanation. Sigh.

Just like the first Industrial Revolution, this will change the world in profound and unexpected ways.

Why your first launch might not be enough.

Although design systems promise consistency, most still fail without someone actively enforcing the rules and making teams follow them.

Making changes that actually work instead of optically sounding impressive.

Wait, we have AI now. We don’t have to say no to 1,000 things. We can say yes to all the things — generate them all, simultaneously!!!1

Most design system roles are design-focused, but the biggest value comes from code. Are we building design systems, or just designing them?

I put a post-mortem in your post-mortem.

Software is problem ownership.

Formats over apps.

Clothes have never been cheaper. Same thing is happening with software.

It’s January, and millions of people have made the same resolution: “Eat better.” By February, most will have abandoned it.

Generic software design advice is typically useless for most practical software design problems.