Mac@programming.dev to Programming@programming.dev · edit-210 months agoLet'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-210 months agomessage-square75fedilink
minus-squarejonne@infosec.publinkfedilinkarrow-up2·10 months agoWhich definitely wouldn’t have been a single developer’s fault.
minus-squaregedhrel@lemmy.worldlinkfedilinkarrow-up3·10 months agoDevelopers aren’t the ones at fault here.
minus-squareMiaou@jlai.lulinkfedilinkarrow-up1·9 months agoNot the most at fault, but if you sign off on a shitty process, you are still partially responsible
minus-squaregedhrel@lemmy.worldlinkfedilinkarrow-up1·9 months agoThat depends entirely on the ability to execute change. CTO is the role that should be driving this.
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.