Mac to [email protected] • edit-22 months agoLet's blame the dev who pressed "Deploy" - by Dmitry Kudryavtsevyieldcode.blogexternal-linkmessage-square72fedilinkarrow-up1263arrow-down113
arrow-up1250arrow-down1external-linkLet's blame the dev who pressed "Deploy" - by Dmitry Kudryavtsevyieldcode.blogMac to [email protected] • edit-22 months agomessage-square72fedilink
minus-square@gedhrellink5•2 months agoPossibly 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-square@[email protected]linkfedilink2•2 months agoWhich definitely wouldn’t have been a single developer’s fault.
minus-square@[email protected]linkfedilink1•1 month agoNot the most at fault, but if you sign off on a shitty process, you are still partially responsible
minus-square@gedhrellink1•1 month agoThat 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.