@Brkdncr@lemmy.world to Technology@lemmy.worldEnglish • 1 year agoLet's blame the dev who pressed "Deploy"yieldcode.blogexternal-linkmessage-square60fedilinkarrow-up1280arrow-down113
arrow-up1267arrow-down1external-linkLet's blame the dev who pressed "Deploy"yieldcode.blog@Brkdncr@lemmy.world to Technology@lemmy.worldEnglish • 1 year agomessage-square60fedilink
minus-square@Geyser@lemmy.worldlinkfedilinkEnglish14•1 year agoWas there a process in place to prevent the deployment that caused this? No: blame the higher up Yes: blame the dev that didn’t follow process Of course there are other intricacies, like if they did follow a process and perform testing, and this still occurred, but in general…
minus-square𞋴𝛂𝛋𝛆linkfedilinkEnglish32•1 year agoIf they didn’t follow a procedure, it is still a culture/management issue that should follow the distribution of wealth 1:1 in the company.
Was there a process in place to prevent the deployment that caused this?
No: blame the higher up
Yes: blame the dev that didn’t follow process
Of course there are other intricacies, like if they did follow a process and perform testing, and this still occurred, but in general…
If they didn’t follow a procedure, it is still a culture/management issue that should follow the distribution of wealth 1:1 in the company.