[swatcoder]

> This alone gave me 90% of the finished product

The Claude the industry needs is one that responds to that prompt with questions about scope and intent, and challenges its only-suitable-for-tutorials design ideas rather than obediently delivering a "90% finished product".

10 years ago, this basically marks the difference between hiring some dude on Fiverr for $400 and an actual engineer or agency who might help you figure out what the heck you're trying to do and point you in some sane direction towards it.

I appreciate this article for sharing what kind of experience people can expect from Claude right now, but it mostly demonstrates that code assistants remain most useful in the hands of experts who are careful what to ask for, and largely misleading and slop-amplifying for people who don't.

[Jeremy1026]

It'd be an interesting follow up to have one of my kids give me prompts to make the same application and see how well it does. As in, when it doesn't save and they say "it's not working." How would it react and try to problem solve.

[rfw300]

Claude Code's Plan Mode increasingly does a (small-scale) version of this - it will research your codebase and come back to you with a set of clarifying questions and design decisions before presenting its implementation plan.

[benburleson]

I've found the most useful prompt tip is to add to the end of every prompt:

"Ask questions for clarification as needed."

Claude will then present a list of questions I answer, either directly, or sometimes those prompt more thought or questions from myself.

Either way, that statement helps escape the assumption that I just want some slop reaching the goal in the quickest way possible.