Comment on The Great Software Quality Collapse: How We Normalized Catastrophe
GenosseFlosse@feddit.org 12 hours agoYou never worked onrold code. It’s never that simple in practice when you have to make changes to existing code without breaking or rewriting everything.
Sometimes the client wants a new feature that cannot easily implement and has to do a lot of different DB lookups that you can not do in a single query. Sometimes your controller loops over 10000 DB records, and you call a function 3 levels down that suddenly must spawn a new DB query each time it’s called, but you cannot change the parent DB query.
PattyMcB@lemmy.world 11 hours ago
That’s why it needs to be written better in the first place
GenosseFlosse@feddit.org 9 hours ago
Tell me you never worked on legacy code without telling me…
PattyMcB@lemmy.world 8 hours ago
Kid. Go away
Womble@piefed.world 5 hours ago
You do accept that bad software has been written, yes? and that some of that software is performing important functions? So how is saying "It needs to be written better in the first place" of any use at all when discussing legacy software?