| ▲ | kaydub 4 hours ago | |||||||||||||
Yeah, v1 is sloppy, then I tell the LLM to clean it up. Every 1 prompt of building tends to require 1-5 prompts of clean up. Simple, fast, clean good code. The chasm between "Software Developer" and "Software Engineer" is getting wider. Articles like this and the comments under it give away who is an Engineer and who is just a coder. | ||||||||||||||
| ▲ | rspeele 2 hours ago | parent | next [-] | |||||||||||||
> Every 1 prompt of building tends to require 1-5 prompts of clean up. Simple, fast, clean good code. I have found this to be very effective as well. However, it's so easy to do, I can't imagine they won't build it in. The harnesses will improve and the loop of "self-review, judge what needs clean up, do the refactoring, repeat until clean" will get included in the one-shot. They are already doing this somewhat, they'll just get a lot better at it and as the models get faster and cheaper to run, the refactoring churn at the end of each task won't even create a noticeable delay. I do not think the high-level "taste" knowledge that I've built up -- when to break something off into its own service, what to put in the DB vs cache vs queues vs blob storage, how to isolate important logic in pure functional layers so it can be tested and validated independently -- is any more "unlearnable" to AI than the stuff I previously considered impressive that's now one-shottable like "write a Prolog implementation from scratch". | ||||||||||||||
| ||||||||||||||
| ▲ | yesitcan 3 hours ago | parent | prev [-] | |||||||||||||
The chasm is 1-5 prompts wide? | ||||||||||||||
| ||||||||||||||