Didn’t watch but is this the “code doesn’t matter as long as you’re fulfilling customer requirements” take?
Because while there’s a nugget of truth to that (a desired app will always beat a well engineered app that doesn’t do what people want it to) you’ll hit a point where you stall out and can’t build more features and fulfill requirements because of the decisions (or lack thereof) you made before. It’s not an excuse to just throw caution to the wind and make boneheaded decisions.
It’s something that loser vibecoders on LinkedIn all learn the hard way after you get out of the “toy” phase of development.
Didn’t watch but is this the “code doesn’t matter as long as you’re fulfilling customer requirements” take?
Because while there’s a nugget of truth to that (a desired app will always beat a well engineered app that doesn’t do what people want it to) you’ll hit a point where you stall out and can’t build more features and fulfill requirements because of the decisions (or lack thereof) you made before. It’s not an excuse to just throw caution to the wind and make boneheaded decisions.
It’s something that loser vibecoders on LinkedIn all learn the hard way after you get out of the “toy” phase of development.