| ▲ | sathish316 3 hours ago | |
This is the best summary of everything that’s wrong with: 1. One-shot app development using Lovable with English requirements 2. Spec driven development tools like SpecKit, Kiro that promise English as being sufficient for LLM generated code 3. Using agent swarms with Claude Code and thinking you are making progress and you never have to look at the generated code, when the overall coherence or elegance of the codebase is lost. Loved the analogies in this video: “It looks like an airplane. It flies like an airplane. But when you inspect the code in its full context, it’s a paper plane.” and “It looks like an airplane, walks like an airplane and talks like an airplane. It’s probably an airplane. But it’s not an airplane, it’s a psychedelic airplane …filled with hallucinations” But, still the tools are incredibly helpful when you have the right guardrails and take the time to ensure (somehow) the output matches your taste and code quality expectations. | ||
| ▲ | AstroBen 2 hours ago | parent [-] | |
Elegance or "taste" for the codebase is wrong. It's not just a stylistic preference. It's objectively bad code that's going to be slow to iterate on and very easy to introduce bugs to I'm not saying AI has no place, but letting it take the lead in any way is just building your app on sand. Fine if you're building a sandcastle, bad if you're building a bridge. It's not "ohh well I just don't like the way sandcastles look" | ||