sounds like he’s frustrated that a clean architecture didn’t magically solve all of his problems
I wonder if anyone actually watched the video or you’re all just knee jerking to the title…?
He’s not saying that you should write or accept spaghetti code, he’s sharing a particular story from his career that he learned from where in that specific case the old spaghetti implementation beat the new architecturally pure, perfect code standards version - because the developer of the new one only focused on that and not observability, proper load testing, designing for the right scale, etc.
The point is clearly that code quality is one of multiple important factors.
I thought it was a perfectly reasonable watch.
Edit: referring mainly to the down votes, there are others in the comments who clearly watched it.
Sounds like observability, proper load testing, etc. beat a system without that. Saying that spaghetti code beat clean code makes it sound like it won because it was spaghetti code.
I haven’t watched the video, nor am I going to with a clickbaity and apparently misleading title like that.
There’s literally 8 replies, why are you speaking into the void like you’re addressing hundreds of opinions?
I specifically said I’m referring to the large number of down votes.
Not our problem, if the title is rage baiting and missleading.
Why not interchange ‘Why’ with ‘When’…
If I post: ‘Lemmy communities suck’ as a Youtube video (arguing against someone, who said this), which should not be posted at Lemmy (as it is big tech and full of trackers), I’m the on, who have to live with the consequences.
Of course he’s trying to get our attention, but I don’t think the title is incorrect? Why the spaghetti one beat the clean one is what he talked about.
If he’s said “beats” I’d be upset too, but a singular “beat” makes it fine in my opinion.
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.
Backend engineering code quality does not matter.
X
What a ridiculous take, thanks for saving me the time
The system failed because they didn’t capture all the requirements and did some lazy testing and a shitty “MVP”
They tested against MOCKS and then went to prod! Fuckn’ QA is there for a reason.
no. you’re trash.
