Three dominant themes in the discussion
| # | Theme | Key points & representative quotes |
|---|---|---|
| 1 | Planning + specification is essential before any code is written | • “never let Claude write code until you’ve reviewed and approved a written plan” – RHSeeger • “I always work towards an approved plan before I let it write code” – RHSeeger • “The annotation cycle is the key insight for me. Treating the plan as a living doc you iterate on before touching any code” – dennisjoseph |
| 2 | Structured workflows and tooling (tickets, plan files, agents) keep the process organized | • “I use a ticket system basically like ticket_ • “I let the agent create the ticket from a chat, correct and annotate it afterwards and send it back” – zitrusfrucht • “I use a specific format in the /plan command, by using the ME: prefix” – srid • “I use a ticket system… this workflow helps me keeping track of what has been done over time” – zitrusfrucht |
| 3 | Human oversight and cost‑efficiency remain critical; AI is a tool, not a replacement | • “I think it is far more work than just writing the code yourself” – jamesmcq • “I had to manually test that it worked, and it did. I then needed to review the code before making a PR” – shepherdjerred • “I burned through $10 on Claude in less than an hour” – raw_anon_1111 • “I’m still skeptical that LLMs can produce maintainable, secure, performant code without heavy human review” – jamesmcq |
These three themes—rigorous pre‑coding planning, disciplined workflow tooling, and the continued need for human judgment and cost awareness—capture the core of the conversation.