[daliboru]

I see a similar issue in 2025, but with vibe coding.

It all boils down to the 3 key factors: speed, quality and cost. And you can't have it all

Know your trade-offs.

[layer8]

How do you achieve speed and quality at the same time?

[daliboru]

To quote one movie character: "Bro, when you can't fix a problem with money, you fix it with a lot of money."

Jokes aside, you find the crème de la crème of engineering, and pay as much as they ask for.

Speed + Quality = $$$$$

On the other hand,

Speed + Cheap = Crap Quality

Cheap + Quality = Slow

[Tepix]

With vibe coding, you have none of those. The initial speed advantage will disappear once you need to maintain the mess.

[daliboru]

Tnx for the comment. Discussing tools (in this case, vibe coding) naturally raises the issue of what skills are actually needed to use them effectively, such as prompting, which in turn leads to a broader question about the role and relevance of traditional software engineering skills. It's a whole other topic...

You can create value with vibe coding. As I said, know your trade-off, your context.

You wouldn't use a hammer to fix a watch, would you?