Martin Seeger@masek@infosec.exchange
If you come with a complex problem to an experienced coder, he will ask you a lot strange questions.
He doesn't just want to spit out the code you requested, but to understand the core problem.
Usually those questions will annoy you. It will make your problem uglier and dirtier than you thought and will ruin the beautiful solution you have in mind. But that approach gives you the chance to get you a real solution.
The AI doesn't ask you all those pesky questions. It doesn't want to understand the problem and just spits out code.
I understand the appeal of that ... and the risks.
Turre@Turre@mementomori.social
@masek@infosec.exchange Amusingly, Claude Code quickstart contains the following Pro Tip! to beginners:
"Before making changes, let Claude understand your code:"
...with examples such as "analyze the database schema".
Would you need to specifically ask for such things if there was anything resembling intelligence in the machine? Your hammer doesn't ask about the nails either.