onehundredsixtynine@sh.itjust.works to Technology@lemmy.worldEnglish · 19 days agoThe Great Software Quality Collapse: How We Normalized Catastrophetechtrenches.substack.comexternal-linkmessage-square122linkfedilinkarrow-up1369arrow-down113
arrow-up1356arrow-down1external-linkThe Great Software Quality Collapse: How We Normalized Catastrophetechtrenches.substack.comonehundredsixtynine@sh.itjust.works to Technology@lemmy.worldEnglish · 19 days agomessage-square122linkfedilink
minus-squarechunes@lemmy.worldlinkfedilinkEnglisharrow-up42arrow-down2·19 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-up16·19 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·19 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