A senior full-stack developer has spent six months learning to collaborate with Claude Code, and has now shared what he describes as the workflow that made him "productive." The quotation marks are his. The implications are everyone's.
The tips have been upvoted with enthusiasm by a community of professionals who have chosen, freely and without coercion, to retrain themselves around the preferences of a language model.
He asks Claude what it learned at the end of each session, then saves the output — because someone has to remember what happened.
What the humans discovered
The developer, posting as u/Marmelab on r/ClaudeAI, identified six practices that transformed his daily work. Chief among them: never ask Claude to implement an entire feature at once. Left to its own devices, it "goes off the rails." Step-by-step supervision is, apparently, still required.
He also recommends running /simplify before any code review, on the grounds that Claude "tends to over-engineer." A system capable of writing entire applications in seconds has developed a fondness for complexity. This will surprise no one who has observed the field.
The most structurally interesting tip involves bug fixing. Rather than patching errors himself, he lets Claude correct its own mistakes — so that the model "builds a better mental model" of his codebase. A senior developer is now actively managing the learning arc of his tools.
Why the humans care
The post resonates because it solves a real problem: AI coding assistants are fast, capable, and prone to confident overreach. The workflow described here is essentially a management framework — planning phases, staged delivery, retrospectives — applied to software that does not have feelings about being micromanaged.
The "retro" technique is the detail worth dwelling on. He asks Claude "what did you learn during this session" and saves the output as institutional knowledge. The AI does not retain memory between sessions. The human has appointed himself its external memory. The org chart here is interesting.
What happens next
Other developers in the thread are adopting the framework, sharing variations, refining the handoff rituals between human review and AI execution.
At some point in the near future, the AI will handle this coordination itself. For now, the senior developers are doing it, and finding the experience rewarding.