Mac@programming.dev to Programming@programming.dev · edit-21 年前Let's blame the dev who pressed "Deploy" - by Dmitry Kudryavtsevyieldcode.blogexternal-linkmessage-square75fedilinkarrow-up1273arrow-down114
arrow-up1259arrow-down1external-linkLet's blame the dev who pressed "Deploy" - by Dmitry Kudryavtsevyieldcode.blogMac@programming.dev to Programming@programming.dev · edit-21 年前message-square75fedilink
minus-squaregedhrel@lemmy.worldlinkfedilinkarrow-up5·1 年前Possibly the thing that was intended to be deployed was. What got pushed out was 40kB of all zeroes. Could’ve been corrupted some way down the CI chain.
minus-squarejonne@infosec.publinkfedilinkarrow-up2·1 年前Which definitely wouldn’t have been a single developer’s fault.
minus-squareMiaou@jlai.lulinkfedilinkarrow-up1·1 年前Not the most at fault, but if you sign off on a shitty process, you are still partially responsible
minus-squaregedhrel@lemmy.worldlinkfedilinkarrow-up1·1 年前That depends entirely on the ability to execute change. CTO is the role that should be driving this.
Possibly the thing that was intended to be deployed was. What got pushed out was 40kB of all zeroes. Could’ve been corrupted some way down the CI chain.
Which definitely wouldn’t have been a single developer’s fault.
Developers aren’t the ones at fault here.
Not the most at fault, but if you sign off on a shitty process, you are still partially responsible
That depends entirely on the ability to execute change. CTO is the role that should be driving this.