Hacker News new | ask | show | jobs
by jwithington 1517 days ago
Because I’m replying to someone who would know what those acronyms are.

The ELI5 is that the Navy pays officers who do the core ship/flying activities quite well. Compared to their civilian peers, Navy lawyers, doctors, and cyber people don’t get paid well.

The posted article is about rust on ships. A ships management team is paid well. Low pay is unlikely to be the cause of dissatisfaction.

To be clear, “paid well” is not “paid well” as measured by FAANG tech salaries. A submarine officer with 8 years of experience is making something equivalent to $200Ks if I am to believe the calculators that adjust for tax advantages of military pay, discounted value of future retirement cash flows, etc.

2 comments

I was a SWO before going into medicine. My first divo tour was in the engineering dept and my second was in weapons. Did well in both. I'm not sure I agree with you about the SWOs or pilots getting paid well relative to their civilian peers.
Maybe it’s ultimately a subjective thing. If one feels underpaid, they are underpaid. Then it’s a matter if there’s an employer that agrees, and it just takes one.

I’d just note that the service academies crowd the rankings for highest paid graduates at early/mid career https://www.payscale.com/college-salary-report/bachelors#ful...

Anecdotally, I had a reservist friend with a Harvard MBA who realized he could pull down more money as an activated reservist in Bahrain than his role at BlackRock.

Your mileage may vary…

"Because I’m replying to someone who would know what those acronyms are."

That only flies in an email or on a specialized forum.

It's curious that you are smart enough to come up with an arguement yet apparently at the same time innocently simple enough not to know why it's invalid.

>That only flies in an email or on a specialized forum.

Counterpoint: It doesn't.

They made a reply to a military member on a thread about military equipment. Googling a few acronyms + "military" would surely lead one to the answer.

It would indeed. But why push the burden onto all the non-specialist readers, who after all come here to both learn and to take part, rather than expand the initialisms the first time they're introduced in a thread?

I'm reminded of an acronym at work: CIM. They come in two variants, CIM-A and CIM-B. I'd been there a year before I finally decided I needed to ask a more senior colleague what they stood for, and he didn't know either. The intention was obvious from the context of their use (although whether -A or -B was more serious wasn't) but most of the people in the weekly meetings discussing Critical Incident Management didn't actually know that was what they were discussing. Nowadays we have a culture that better encourages definition of terms upon first use, and it's less common that someone needs to ask "stupid" questions.

lol I feel like this debate plays out at least weekly in a HN thread about a subculture, specialty, etc.