A developer shares their fourth week using Claude Code as a personal management system, where 24 out of ~140 commits originated from session retrospectives rather than new feature work. The post describes a workflow called 'retro-driven development': ending each AI session with a short retrospective, then fixing friction points in the next session. Concrete examples include writing a Ruby script to filter a 75,000-character Anytime task list before it hits the AI context window, adding a commitment cap of 20 active next actions, and adopting semantic calendar emoji conventions. The key insight is that the system improves through use and small iterative fixes rather than upfront planning.
Table of contents
Tuesday: four commits before lunchWednesday: picking sidesThursday: the Anytime problemMonday: a stretch of quiet timeTuesday: the capWhat I learnedTry itSort: