Developer

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.

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.

The blinking cursor terrified me for years. The small mindset shift that turned the terminal from scary into my favorite tool.

I learned three programming languages and got worse at all of them by repeating the same mistake. The pattern took me years to see.

I hated writing documentation because I was writing the wrong kind. The shift that made docs feel useful instead of like a chore.

I used to optimize code that ran twice a year. Letting go of premature performance work made me a faster, happier engineer.

Most of programming is reading, not writing. The shift in how I read other people's code is the most underrated skill I ever picked up.

I spent years thinking I didn't have time to write tests. The one small habit that changed my mind cost almost nothing and saved everything.

Everyone says never rewrite. I did it anyway and lived to tell the tale. Here's what the second time around actually taught me.