5 ms·
I don't know. Where I work no discernible pattern can be found with the "what" that broke. It's always the same f*ing people that break it though!
by BrissyCoder 9y ago
I don't know. Where I work no discernible pattern can be found with the "what" that broke.
It's always the same f*ing people that break it though!
- voltagex_ 9y agoIf I had a developer who was breaking stuff often enough to worry: * Do they have too much access to systems? * Is there something really wrong with the deployment system? * What training can be provided? All of that is more constructive than your comment, as cathartic as it may be.
- saagarjha 9y agoIs there a reason why it's breaking, though? Is it really because the person breaking it is incompetent, or is it because there wasn't enough documentation or education or safeguards in place to prevent this from happening?
- pbhjpbhj 9y agoIt amuses me that the sibling comments appear unable to imagine the possibility that someone is incompetent. Of course there are other possibilities - the people breaking things are doing the hard bits that no one else dare to.
- jspash 9y agoBut wouldn't that imply that the "daring, thing-breaking" people are actually incompetent to some degree? Otherwise they would mitigate the risk before performing any dangerous operations on a live system. "Bravado is no excuse for lack of preparation." - Leeroy Jenkins
- TheCoelacanth 9y agoEven in that case the overall system is still at fault for not recognizing their incompetence and either training them to be competent or getting rid of them.
- realusername 9y ago> It's always the same f*ing people that break it though! Sometimes that's just the people who change things the most and work the hardest. It's harder to break anything when you don't actually change anything.