onehundredsixtynine@sh.itjust.works to Technology@lemmy.worldEnglish · 5 days agoThe Great Software Quality Collapse: How We Normalized Catastrophetechtrenches.substack.comexternal-linkmessage-square142fedilinkarrow-up1403arrow-down112cross-posted to: [email protected]
arrow-up1391arrow-down1external-linkThe Great Software Quality Collapse: How We Normalized Catastrophetechtrenches.substack.comonehundredsixtynine@sh.itjust.works to Technology@lemmy.worldEnglish · 5 days agomessage-square142fedilinkcross-posted to: [email protected]
minus-squarechunes@lemmy.worldlinkfedilinkEnglisharrow-up46arrow-down2·5 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·5 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·5 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