You can make simple things like that, you can't make good things.
The tools for non-developers to build applications have existed for a long time, those are called no-code tools, and they can do pretty much the same as what non-developers can do with "vibe coding".
The code generated by vibe coding is bad, it has no consistency, it just finds a place to put something and places it there, it has no understanding of architecture, nor anything it's doing... and you may say this doesn't matter, but it's what matters the most.
Understanding what's happening in the application and being able to come up with a mental model of how the system works is fundamental to building software that's maintainable. Without that, you're just stacking bricks without a blueprint — it might stand for a while, but it will collapse under the slightest pressure.
When you rely on tools that generate code without structure, you lose control over the system.
Debugging becomes a nightmare. This is even true for experienced developers, it's harder to debug code you didn't write, and it's exponentially harder to debug code that has no structure.
Extending functionality becomes guesswork. And worst of all, you create technical debt from day one — not because the app is big, but because it's incoherent.
Danny Morabito
npub1ve…xddfh
2025-04-13 10:38:04
in reply to nevent1q…kzmu
Author Public Key
npub1ven4zk8xxw873876gx8y9g9l9fazkye9qnwnglcptgvfwxmygscqsxddfhPublished at
2025-04-13 10:38:04Event JSON
{
"id": "046f36c7c9fe49632d83a73253c3d4d65638bd8c82e4e8816eb366c6141630de",
"pubkey": "66675158e6338fe89fda418e42a0bf2a7a2b132504dd347f015a18971b644430",
"created_at": 1744540684,
"kind": 1,
"tags": [
[
"e",
"035389ec569d03d9cce51c1e1df92ab79441f12a5c5ad602dfafad99f304b108",
"wss://nos.lol",
"root"
],
[
"e",
"62c7a158b9a8a53e59e383f86bbf498d659b60b4586da23dcae633daf807f5da",
"wss://nos.lol",
"reply"
],
[
"p",
"50d94fc2d8580c682b071a542f8b1e31a200b0508bab95a33bef0855df281d63"
],
[
"p",
"1bc70a0148b3f316da33fe3c89f23e3e71ac4ff998027ec712b905cd24f6a411"
]
],
"content": "You can make simple things like that, you can't make good things.\nThe tools for non-developers to build applications have existed for a long time, those are called no-code tools, and they can do pretty much the same as what non-developers can do with \"vibe coding\". \n\nThe code generated by vibe coding is bad, it has no consistency, it just finds a place to put something and places it there, it has no understanding of architecture, nor anything it's doing... and you may say this doesn't matter, but it's what matters the most.\n\nUnderstanding what's happening in the application and being able to come up with a mental model of how the system works is fundamental to building software that's maintainable. Without that, you're just stacking bricks without a blueprint — it might stand for a while, but it will collapse under the slightest pressure.\n\nWhen you rely on tools that generate code without structure, you lose control over the system. \n\nDebugging becomes a nightmare. This is even true for experienced developers, it's harder to debug code you didn't write, and it's exponentially harder to debug code that has no structure.\n\nExtending functionality becomes guesswork. And worst of all, you create technical debt from day one — not because the app is big, but because it's incoherent.",
"sig": "73e17fcb4b39b38bd19954e9a3428a43d5f8a984e3d462421c94bc1e17a46e8ebd06def7a1f4d50e5abe6f989272afc09cfaab91745fe476c3015f6a2e5bd141"
}