hadifrt20

This is exactly the trap. I keep catching myself spending weeks on the tech stack and architecture before I've talked to a single person.. the building feels productive and quite comfortable, it's like a quick reward to us for having an idea without needing to battle test in the field

I spent time on this one because context switching was already my baseline before Claude Code because of the nature of my job; what's worked best: I force myself to ask why I'm launching things in parallel. Is it a real deadline? Back-to-back calls? Or am I just trying to feel more productive? If it's the last one, it's probably not worth it. Very few people actually multitask well. Write the task somewhere ( or have a todo skill that does it for you)

The other piece I picked up from someone writing about this: treat your head like RAM. When you can't avoid a switch, clear it before moving on. Write the note, close the loop, get it out of your head. The lingering open tabs in our heads are the heaviest load, not the switch itself.

honestly, the thing that snapped me out of the AI doom spiral was building something small with it instead of reading about it.

I'll give it a try

in the auickstart, the suggested fixes are called "Prompt Patches" .. does that mean Kelet only surfaces root causes that are fixable in the prompt? What happens when the real bug is in tool selection or retrieval ranking for example?