[agrajag]

You’d be surprised at how much you can fuck up a ship as a CO without life-changing consequences. Unless there’s gross negligence a CO is almost certainly not even going to get discharged even if their actions lead to death of a sailor.

They’ll stop being CO and will never be promoted, but will finish out their Navy career in a job where they can’t hurt anyone, and will have almost no impact once they retire and go into civilian life.

They’re not going to do time in the brig unless there’s willful misconduct.

[sixstringtheory]

I believe you, but still I'd wager a CO has a higher probability of death than Elon Musk due to the conditions of their work.

I looked it up and found this at https://www.history.navy.mil/research/library/online-reading...:

> Commander A. L. Wilderman, CO of USS Plunger (SSN-595), lost overboard in a storm just off San Francisco. 2 December 1973.

Who is the last software CEO that died in the course of their duty specifically due to the nature of their work?

[kortilla]

A commander doesn’t have to go overboard due to the nature of their work. That’s no different than a CEO who happened to have a heart attack while being CEO.

Lookup James Po Ho Cheung or Sid Agrawal if you want examples of CEOs straight up murdered for their roles.

[sixstringtheory]

Of course it’s different. The very nature of a soldier’s job involves death. I don’t understand what you mean by “a CO doesn’t have to go overboard”, I provided an example of just that happening. Anyone on a ship has a nonzero risk of going overboard. Elon Musk has 0 risk of being swept into the sea from his desk.

Every human with a heart has some risk of heart attack. It’s silly to compare that risk to a soldier’s risk of death.

And any CEO that fires someone has a risk of being attacked by that disgruntled former employee.

This is exactly why I said

> software CEO that died in the course of their duty specifically due to the nature of their work

So that example fails the test.

The example of James Po Ho Cheung is more interesting. Now that I think about it, since software can operate in so many different domains, it’s valid that some of those can be dangerous, such as gambling in his case.

[kortilla]

> Of course it’s different. The very nature of a soldier’s job involves death.

Absolutely not as the CO of a ship. You are orders of magnitude safer on one of those ships than working as a roofer or a farmer.

> don’t understand what you mean by “a CO doesn’t have to go overboard”, I provided an example of just that happening.

You provided an example of someone going overboard on a ship, but nothing a CO does makes them more susceptible to going over than any other person on the ship. Being a CO is not higher risk than taking a fucking Carnival cruise.

> Every human with a heart has some risk of heart attack. It’s silly to compare that risk to a soldier’s risk of death.

Given that “heart attack” is probably the most likely way a high level officer in the US military would die, I think not.

> Elon Musk has 0 risk of being swept into the sea from his desk.

Not quite. San Francisco has some pretty gnarly long tail risks from earthquakes. He’s also now in charge of one of the biggest propaganda tools in the history of humanity. The Saudi’s have wacked reporters for far less.

[sixstringtheory]

I think you’ve lost track of the context here and are just trying to refute every sentence in isolation, but I see no coherent refutation of the main idea.