onehundredsixtynine@sh.itjust.works to Technology@lemmy.worldEnglish · 1 day agoThe Great Software Quality Collapse: How We Normalized Catastrophetechtrenches.substack.comexternal-linkmessage-square123fedilinkarrow-up1319arrow-down113
arrow-up1306arrow-down1external-linkThe Great Software Quality Collapse: How We Normalized Catastrophetechtrenches.substack.comonehundredsixtynine@sh.itjust.works to Technology@lemmy.worldEnglish · 1 day agomessage-square123fedilink
minus-squareozymandias117@lemmy.worldlinkfedilinkEnglisharrow-up13·18 hours 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-up4·16 hours 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-up3·15 hours 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?”