zlacker

I really wish posts like this explained what sort of development they are doing. Is this for an internal CRUD server? Internal React app? Scala server with three instances? Golang server with complex AWS configuration? 10k lines? 100k lines? 1M+? Externally facing? iOS app? Algorithm-heavy photo processing desktop app? It would give me a much better idea of whether the argument is reasonable, and whether it is applicable for the kind of software I generally write.

>>prewet+(OP)
You're completely right and I wish I had in retrospect... I was honestly just talking mostly in broad terms, but people really (maybe rightly) focused on the "not reading code" snippet.

I'm mostly developing my own apps and working with startups.

>>prewet+(OP)
The author is a PM with a bachelors in economics who got laid off last year and began building with AI. Zero engineering experience.

You can guess what kind of software he is building.

When you read the 100th blog post about how AI is changing software development, just remember that these are the authors.

>>prewet+(OP)
He makes <10k cloc websites trying to sell you a spec-creation wizard[0]. Considering Claude wrote the site, it could probably be written in 1/10th of the lines.

I think these tools are great for allowing non-technical people like OP to create landing pages and small prototypes, but they're useless for anything serious. That said, I applaud OP for embodying the "when in a gold rush, sell shovels" mentality.

[0] - https://vibescaffold.dev/