2026

Dropped into a huge unfamiliar codebase? Here's the exact week-one playbook I use to go from lost to shipping, without reading every file.

For thirty days, nobody on my team sat in a status meeting. An AI ran them instead. Here's what broke, what got better, and what I'll never go back to.

One weekend, zero code, and an AI agent that now handles a task I used to dread every Monday. Here's exactly how I did it.

The honest result of waking at 5 AM for a month — including the part nobody mentions when they sell you the dream.

A small, unglamorous AI stack that quietly does about an hour of work before I've finished my coffee. Here's the exact lineup and what each one does.

Three days. One bug. The fix was a single character. Here's the full story and the debugging lessons I wish I'd learned before, not after.

I stopped doing the busywork and let AI assistants run the boring half of my job for a month. The results were not what I bragged about on day one.

I tracked every working hour for 30 days, expecting to learn I code a lot. The data said something far more uncomfortable about how I actually spend my day.

I opened a PR I was proud of. The review that came back rearranged how I think about being a good engineer. Here's the whole uncomfortable story.

The pragmatic balance between purity and progress. When chasing perfect code becomes the thing that stops you from shipping.

There are only two hard problems in computer science, and one of them quietly wrecks codebases. Here's why naming is so brutal and how to get good at it.

I ask it in every review and design doc now. One deceptively simple question that quietly upgraded how I build software.