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.
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.
Picking depth over novelty changed my trajectory. Here's how framework FOMO was quietly capping my growth — and what I do instead now.
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.
