my current favorite trick for reducing "cognitive debt" (h/t @simonw ) is to ask the LLM to write two versions of the plan:
- The version for it (highly technical and detailed)
- The version for me (an entertaining essay designed to build my intuition)
I don't know about them, but I would be offended if I was planning something with a collaborator, and they decide to give me a dumbed down, entertaining, children's storybook version of their plan while keeping all the technical details to themselves.
Also, this is absolutely not what "cognitive debt" means. I've heard technical debt refers to bad design decisions in software where one does something cheap and easy now but has to constantly deal with the maintenance headaches afterwards. But the very concept of working through technical details? That's what we call "thinking". These people want to avoid the burden of thinking.
This was not such an effective venture.