jerryharri
Re:How I use Claude Code: Separation of planning and execution
on Sunday February 22, 2026 @03:00PM (#47114102)
Be careful of attention collapse. Details in a large governance file can get "forgotten" by the llm. It'll be extremely apologetic when you discover it's failed to follow some guardrails you specified, but it can still happen.
Re:How I use Claude Code: Separation of planning and execution
on Sunday February 22, 2026 @10:03AM (#47111554)
It's after we come down from the Vibe coding high that we realize we still need to ship working, high-quality code. The lessons are the same, but our muscle memory has to be re-oriented. How do we create estimates when AI is involved? In what ways do we redefine the information flow between Product and Engineering?
Re:How I use Claude Code: Separation of planning and execution
on Sunday February 22, 2026 @07:36AM (#47110514)
We're learning the lessons of Agile all over again.
Re:How I use Claude Code: Separation of planning and execution
on Sunday February 22, 2026 @07:35AM (#47110503)
'The post is quite waterfall-like. Writing a lot of docs and specs upfront then implementing' - It's only waterfall if the specs cover the entire system or app. If it's broken up into sub-systems or vertical slices, then it's much more Agile or Lean.