Mac@programming.dev to Programming@programming.dev · edit-22 years agoLet's blame the dev who pressed "Deploy" - by Dmitry Kudryavtsevyieldcode.blogexternal-linkmessage-square74linkfedilinkarrow-up1268arrow-down114
arrow-up1254arrow-down1external-linkLet's blame the dev who pressed "Deploy" - by Dmitry Kudryavtsevyieldcode.blogMac@programming.dev to Programming@programming.dev · edit-22 years agomessage-square74linkfedilink
minus-squarejonnelinkfedilinkarrow-up2·2 years agoWhich definitely wouldn’t have been a single developer’s fault.
minus-squaregedhrel@lemmy.worldlinkfedilinkarrow-up3·2 years agoDevelopers aren’t the ones at fault here.
minus-squareMiaou@jlai.lulinkfedilinkarrow-up1·2 years agoNot the most at fault, but if you sign off on a shitty process, you are still partially responsible
minus-squaregedhrel@lemmy.worldlinkfedilinkarrow-up1·2 years 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.