onehundredsixtynine@sh.itjust.works to Technology@lemmy.worldEnglish · 2 months agoThe Great Software Quality Collapse: How We Normalized Catastrophetechtrenches.substack.comexternal-linkmessage-square141fedilinkarrow-up1408arrow-down112cross-posted to: [email protected]
arrow-up1396arrow-down1external-linkThe Great Software Quality Collapse: How We Normalized Catastrophetechtrenches.substack.comonehundredsixtynine@sh.itjust.works to Technology@lemmy.worldEnglish · 2 months agomessage-square141fedilinkcross-posted to: [email protected]
minus-squarechunes@lemmy.worldlinkfedilinkEnglisharrow-up47arrow-down2·2 months 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·2 months 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·2 months 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