Tech & Software

AI can write the code now. The one skill that got more valuable, not less, is the thing nobody put on a tutorial list.

Not the flashiest build — the one that proved I could ship. Here's the unglamorous project that did more for my career than three years of interviews.

I split a small app into microservices to look serious. It cost us a year. Here's the architecture mistake I'd warn every engineer about.

I finished hundreds of tutorials and still couldn't build anything alone. The problem wasn't me. It was the format.

Burnout in dev work rarely comes from the obvious causes. Here are the quiet ones nobody puts in a retro — and the specific changes that pulled me out.

Bootcamps teach syntax, frameworks, and data structures. They skip the one skill that separates people who ship from people who stall — and it's learnable.

I faked my way through async code for years. The mental model that finally made it click had nothing to do with threads or syntax. Here it is.

Becoming senior is less about code than anyone tells you. Here's the uncomfortable shift that actually got me there — and the myth that held me back for years.

For 14 days I wrote no code by hand — only AI did. It was faster than I expected and broke in ways I didn't. Here's the honest report.

Most refactors are vanity projects that never pay back. This one did — and the difference taught me when rewriting code is actually worth it.

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.

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 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.

The strangler approach that avoided a risky rewrite. How we modernized a decade-old system without ever stopping it.

The real multiplier is more learnable than talent. What actually separates the engineers who seem to do the work of ten — and why you can copy it.

Indexes, transactions and joins stopped being scary. The mental models that turned the database from a black box into a tool I actually control.