onehundredsixtynine@sh.itjust.works to Technology@lemmy.worldEnglish · 3 months agoThe Great Software Quality Collapse: How We Normalized Catastrophetechtrenches.substack.comexternal-linkmessage-square123fedilinkarrow-up1368arrow-down113cross-posted to: programming@beehaw.orgprogramming@programming.dev
arrow-up1355arrow-down1external-linkThe Great Software Quality Collapse: How We Normalized Catastrophetechtrenches.substack.comonehundredsixtynine@sh.itjust.works to Technology@lemmy.worldEnglish · 3 months agomessage-square123fedilinkcross-posted to: programming@beehaw.orgprogramming@programming.dev
minus-squareanamethatisnt@sopuli.xyzlinkfedilinkEnglisharrow-up12·3 months agoThat and also man hour costs versus hardware costs. It’s often cheaper to buy some extra ram than it is to pay someone to make the code more efficient.
That and also man hour costs versus hardware costs. It’s often cheaper to buy some extra ram than it is to pay someone to make the code more efficient.