onehundredsixtynine@sh.itjust.works to Technology@lemmy.worldEnglish · 2 months agoThe Great Software Quality Collapse: How We Normalized Catastrophetechtrenches.substack.comexternal-linkmessage-square32linkfedilinkarrow-up115arrow-down10cross-posted to: programming@beehaw.orgprogramming@programming.devhackernews@lemmy.bestiver.se
arrow-up115arrow-down1external-linkThe Great Software Quality Collapse: How We Normalized Catastrophetechtrenches.substack.comonehundredsixtynine@sh.itjust.works to Technology@lemmy.worldEnglish · 2 months agomessage-square32linkfedilinkcross-posted to: programming@beehaw.orgprogramming@programming.devhackernews@lemmy.bestiver.se
minus-squarethemaninblack@lemmy.worldlinkfedilinkEnglisharrow-up1·2 months agoBeing obtuse for a moment, let me just say: build it right! That means minimalism! No architecture astronauts! No unnecessary abstraction! No premature optimisation! Lean on opinionated frameworks so as to focus on coding the business rules! And for the love of all that is holy, have your developers sit next to the people that will be using the software! All of this will inherently reduce runaway algorithmic complexity, prevent the sort of artisanal work that causes leakiness, and speed up your code.
Being obtuse for a moment, let me just say: build it right!
That means minimalism! No architecture astronauts! No unnecessary abstraction! No premature optimisation!
Lean on opinionated frameworks so as to focus on coding the business rules!
And for the love of all that is holy, have your developers sit next to the people that will be using the software!
All of this will inherently reduce runaway algorithmic complexity, prevent the sort of artisanal work that causes leakiness, and speed up your code.