> I think back to coworkers I’ve had over the years, and their varying preferences. Some people couldn’t start coding until they had a checklist of everything they needed to do to solve a problem. Others would dive right in and prototype to learn about the space they would be operating in.

This is the interesting question for me. I've had the impression that you should always have a plan, coming from big tech where a plan is demanded of anything significant, but working at a startup again where there's no bureaucracy to force me to do so, I find that I can live without detailed plans just fine. Then again, I am more experienced.

What do you do if Codex goes off and does something using the wrong approach? You've wasted 30 minutes instead of the 5 that you'd use with Claude Code to start iterating.