3 ms·
But this is not “absolutely everything”. No one is saying CEOs should be accountable for every action of an individual employee. So if not the CEO, who is acco
by nkrisc 10mo ago
But this is not “absolutely everything”. No one is saying CEOs should be accountable for every action of an individual employee.
So if not the CEO, who is accountable when something like this breach happens? The CTO? The PM The DBA? Nobody? Maybe they’ll care developer who wrote the code or botched the configuration should be prosecuted?
CEOs can justify their pay be being accountable for what their company does. They’re the CEO, after all. Maybe they’ll care more when they have some actual skin in the game.
- galangalalgol 10mo agoWhen a bridge fails, it is the professional engineer that signed off on that part. If you want someone to sign off on software or IT you will need to pay them quite a lot.
- nkrisc 10mo agoYes, I would expect compensation to increase proportionally with accountability. What makes no sense is compensation that increases irrespective of accountability. Being the CEO of a company that handles risky, sensitive things should be risky for the CEO, personally. And their compensation can reflect that.
- QuantumNomad_ 10mo agoIn other words, they need to hire people whose job it is to “please”. Provide Legal Exculpation and Sign Everything https://how-i-met-your-mother.fandom.com/wiki/Provide_Legal_Exculpation_and_Sign_Everything https://how-i-met-your-mother.fandom.com/wiki/Provide_Legal_...
- nkrisc 10mo agoThat could be outlawed as well as it probably wouldn’t be too difficult to show that person wasn’t actually making any of the decisions. Not that I expect any of this will ever happen.
- antod 10mo agoIn my experience civil engineers get paid less than software developers of equivalent experience or responsibility.
- galangalalgol 9mo agoYes, but they are good at what they do. Software is more conplex and has a culture of fix it in production that would make it far more risky to sign.
- antod 9mo agoI wouldn't describe software as most people experience it as more complex. And civil engineering projects are constantly fixing unforeseen design problems either during construction or afterwards. I would distinguish the failure modes as different though eg analog vs digital. Real world engineering can absorb an awful lot of minor mistakes through safety factors etc. Failure can be gradual or just a matter of degree or even just interpretation of standards. Software failures are often more digital or only matter when "under attack"