Mac@programming.dev to Programming@programming.dev · edit-24 months agoLet's blame the dev who pressed "Deploy" - by Dmitry Kudryavtsevyieldcode.blogexternal-linkmessage-square75fedilinkarrow-up1268arrow-down114
arrow-up1254arrow-down1external-linkLet's blame the dev who pressed "Deploy" - by Dmitry Kudryavtsevyieldcode.blogMac@programming.dev to Programming@programming.dev · edit-24 months agomessage-square75fedilink
minus-squareByteOnBikes@slrpnk.netlinkfedilinkarrow-up44·4 months agoIt’s never a single person who caused a failure.
minus-squarejonne@infosec.publinkfedilinkarrow-up4·4 months agoYeah exactly. You’d think they’d have a test suite before pushing an update, or do a staggered rollout where they only push it to a sample amount of machines first. Just blaming one guy because you had an inadequate UAT process is ridiculous.
minus-squareThe Snark Urge@lemmy.worldlinkfedilinkEnglisharrow-up2·4 months agoAllow me to introduce myself
It’s never a single person who caused a failure.
Yeah exactly. You’d think they’d have a test suite before pushing an update, or do a staggered rollout where they only push it to a sample amount of machines first. Just blaming one guy because you had an inadequate UAT process is ridiculous.
Allow me to introduce myself