Content pfp
Content
@
https://opensea.io/collection/dev-21
0 reply
0 recast
2 reactions

androidsixteen pfp
androidsixteen
@androidsixteen.eth
The thing that gets me about vibecoding is that in order to go fast, you have to relinquish the desire to understand everything / read the code thoroughly This is good in the short run (eg. you have to ship something quick) but bad in the long run because: 1. It’s intellectually less gratifying 2. The tech debt will murder you
11 replies
3 recasts
55 reactions

HH pfp
HH
@hamud
Vibe coding is excellent for when you have a very clear picture of what you want to create as Ai has a really bad tendency of overengineering things and writing too much code. If you don't really know what you want you'll end up in a complete mess as ai will be forced to make those assumptions for you.
1 reply
0 recast
3 reactions

androidsixteen pfp
androidsixteen
@androidsixteen.eth
Problem is that with any project of large enough scope and speed, you will get to a point where your picture is fuzzy So it's very good for one-of mini apps (eg. content) but not very good for large apps (eg. architecture)
0 reply
0 recast
4 reactions