[saalweachter]

I'm not really impressed by someone going to jail for accepting bribes, even if it's less likely to happen in the private sector.

Show me someone going to jail for bringing down prod or making the wrong architecture call or choosing the wrong platform/backend/language or even just getting burnt out and spending a week on the clock re-watching all of Star Trek: Voyager. I want to go, "Holy shit, that could have been me!", not "Well no shit he went to jail."

[vdqtp3]

> just getting burnt out and spending a week on the clock re-watching all of Star Trek: Voyager

That's a Tuesday for some GS folks. Not all, some of the best folks I ever worked with were GS11-12's. Some of the worst also. Very few in the middle.

[soverance]

The company I work for (high profile private sector U.S. defense contractor) has security people (FSOs and such) that are constantly concerned about being held legally responsible for actions (or inactions) related to theirs and other's work (specifically those with personal or facility security clearances). They regularly claim that they can be held responsible for the failures of others.

Their hesitation leads me to believe these legal repercussions happen more often than not. Would be interesting to see some data on the claims. My guess is the people being held responsible for these things aren't your average developer taking down prod.

[nradov]

That's a separate issue. There are criminal and administrative penalties for mishandling classified information that apply to anyone with a clearance, regardless of whether they are a government employee or private contractor. As long as you follow all the rules yourself you won't be punished for someone else's actions.

[adolph]

> As long as you follow all the rules yourself

Sounds easy. Just keep a list in front of me. Maybe a book. Throw it into a RAG on local ollama. Keep a Teams chat open with the compliance folks.

[jachee]

https://news.ycombinator.com/item?id=40951064