> Because the simple act of having to write the thing or seeing it being built up step by step introduces friction that allows you to better understand what you

> Because the simple act of having to write the thing or seeing it being built up step by step introduces friction that allows you to better understand what you want to build [...] I would go further and remove that second option. If the code is important, LLM support or not, write it yourself. At least for me, there is a clear qualitative difference in thinking between typing the code and watching it being typed, even if I follow along with every line. If I type it, my brain is constantly questioning whether what I'm doing is correct. What are the edge cases here? Is this introducing a vulnerability? Am I getting the right data from the right place? By watching an agent or someone else code, the mindset is different. I'm checking someone else's work under the implicit assumption that they have some idea of what they're doing and I'm just reviewing mostly for superficial stuff. I can force myself to ask those other questions, but it takes conscious effort and isn't sustainable over long sessions. I play around with agentic coding, but I'm always shocked at how much worse the result is compared to working in a separate chat and typing (not pasting!) the suggestions. In the direct comparison, it's easy to see how agentic code turns so incredibly shit so ridiculously fast.