Blog
#Productivity
5 post(s)
-
AI That Implements Without Hesitation — How to Write a 20-Section, 3,500-Line Design Doc
Publishing the structure of the design doc that reduced 16 person-days to 2 hours in AI-driven development. The roles and priorities of 20 sections, and the 'must-write' points for each.
-
16 Person-Days of Development Done in 2 Hours — Design Doc Completeness Determines Speed
In a personal project, AI-driven development completed 16 person-days of work in 2 hours. The biggest factor wasn't AI speed — it was the completeness of the design document that eliminated all decision-making.
-
Don't Bring Motivation to Work — Deliver Consistent Results Through Systems, Like Brushing Your Teeth
Motivation-driven action inevitably burns out. Understanding how self-preservation instincts block change, and how systematizing actions like brushing teeth enables consistent output regardless of mood.
-
"Essentialism" and "Effortless" — The Two Wheels of What to Do and How to Do It
Reading Essentialism (what to do) and Effortless (how to do it), I explored how to focus on essential tasks and build systems to make them easier. Applying the Pickle Jar Theory, 10,000-hour rule, and broaden-and-build theory to engineering work.
-
"The Testing Phase Disappeared" — AI-Driven vs Traditional Development Compared
A developer with zero Flutter experience used Claude Code to ship a production app in 3 weeks. This article compares every phase — from planning to testing — with real data showing 6-9x faster delivery and 6x higher test density.