Thoughtful writing for developers

6 weekends, 3 dead repos, and the validation framework I wish I'd used before writing a single line of code. A guide for devs with day jobs.

I tracked commits, bugs, and focus time for 7 months testing productivity systems. Pomodoro tanked my output by 18%. Here's what actually worked.

Your manager says 'not yet' because you're missing what promotion committees actually evaluate. Here's how to reverse-engineer their decision process.

I stayed mid-level for 4 years because I confused competence with growth. Here's what actually separates engineers who thrive from those who plateau.

The loudest developers aren't the most respected. After 6 months offline, I found what actually builds career authority—and it's not posting daily.

I tested 8 PKM tools during real debugging sessions. Obsidian won for most devs, but Logseq surprised me for daily work logs. Here's what actually works.

After 50+ FAANG system design interviews, here's the actual rubric interviewers use—and the 90-day prep plan that matches it.

I tracked my calendar in both roles. The coding time difference isn't what you'd expect, but one question in my 5-point framework made the choice obvious.

I spent 20 minutes writing thorough API docs. A week later, my teammate asked the same question. Here's what I changed about how I write documentation.

Three weeks into my first manager role, I hid in a bathroom stall. Here's everything about the transition to engineering leadership that no one warns you about.