onehundredsixtynine@sh.itjust.works to Technology@lemmy.worldEnglish · 24 days agoThe Great Software Quality Collapse: How We Normalized Catastrophetechtrenches.substack.comexternal-linkmessage-square142linkfedilinkarrow-up11arrow-down10cross-posted to: programming@beehaw.orgprogramming@lemmy.ml
arrow-up11arrow-down1external-linkThe Great Software Quality Collapse: How We Normalized Catastrophetechtrenches.substack.comonehundredsixtynine@sh.itjust.works to Technology@lemmy.worldEnglish · 24 days agomessage-square142linkfedilinkcross-posted to: programming@beehaw.orgprogramming@lemmy.ml
minus-squareozymandias117@lemmy.worldlinkfedilinkEnglisharrow-up0·23 days agoWe’ll just set up another retrospective meeting and have a lessons learned. Then we won’t change anything based off the findings of the retro and lessons learned.
minus-squarePattyMcB@lemmy.worldlinkfedilinkEnglisharrow-up0·23 days agoPost-mortems always seemed like a waste of time to me, because nobody ever went back and read that particular confluence page (especially me executives who made the same mistake again)
minus-squareshalafi@lemmy.worldlinkfedilinkEnglisharrow-up0·23 days agoPost mortems are for, “Remember when we saw something similar before? What happened and how did we handle it?”
We’ll just set up another retrospective meeting and have a lessons learned.
Then we won’t change anything based off the findings of the retro and lessons learned.
Post-mortems always seemed like a waste of time to me, because nobody ever went back and read that particular confluence page (especially me executives who made the same mistake again)
Post mortems are for, “Remember when we saw something similar before? What happened and how did we handle it?”