onehundredsixtynine@sh.itjust.works to Technology@lemmy.worldEnglish · 26 days agoThe Great Software Quality Collapse: How We Normalized Catastrophetechtrenches.substack.comexternal-linkmessage-square141fedilinkarrow-up1407arrow-down112cross-posted to: programming@beehaw.orgprogramming@programming.devhackernews@lemmy.bestiver.se
arrow-up1395arrow-down1external-linkThe Great Software Quality Collapse: How We Normalized Catastrophetechtrenches.substack.comonehundredsixtynine@sh.itjust.works to Technology@lemmy.worldEnglish · 26 days agomessage-square141fedilinkcross-posted to: programming@beehaw.orgprogramming@programming.devhackernews@lemmy.bestiver.se
minus-squarechunes@lemmy.worldlinkfedilinkEnglisharrow-up48arrow-down2·26 days agoSoftware has a serious “one more lane will fix traffic” problem. Don’t give programmers better hardware or else they will write worse software. End of.
minus-squarenelson@lemmy.worldlinkfedilinkEnglisharrow-up19·26 days agoThis is very true. You don’t need a bigger database server, you need an index on that table you query all the time that’s doing full table scans.
minus-squarePattyMcB@lemmy.worldlinkfedilinkEnglisharrow-up1·26 days agoOr sharding on a particular column
Software has a serious “one more lane will fix traffic” problem.
Don’t give programmers better hardware or else they will write worse software. End of.
This is very true. You don’t need a bigger database server, you need an index on that table you query all the time that’s doing full table scans.
Or sharding on a particular column