NASA Force • Hacker News Board

Re: NASA Force

#341

Post by tjwebbnorfolk » Thu, Apr 23, 2026, 5:03 AM UTC

leptons wrote: post #133

itsdesmond wrote: post #101

Earlier quoted context omitted.

It’s not that you’re willfully ignorant of the critique, you already know what it is. It’s TDS. Case closed. Pre-sorting all criticism as reflexive and not necessarily justified is a rationalization for you not trying to understand other perspectives. Edit: it seems like my message was ambiguous. Fuck Donald Trump, I’ve got a bottle to pop when he dies and I’ll never let you fuckers live down what you’ve done.

"TDS" is not a thing. It's a made-up term that people accuse others of, because they can't cover up a felonious president's many failings, lies, graft, and corruption. You use it to try to discredit a person who is rightly criticizing criminality, but you only discredit yourself when you use "TDS".

The link in this post is to a website NASA is using to try to hire engineers.

Your comment is about how much you hate Trump.

TDS is a phenomenon where people have to bring up how much they hate Trump in every conversation, even when it is unrelated to the topic at hand.

Re: NASA Force

#342

Post by OhMeadhbh » Thu, Apr 23, 2026, 7:10 PM UTC

jimmydddd wrote: post #180

DaiPlusPlus wrote: post #162

Earlier quoted context omitted.

> I wrote code and passed it off to a dev in India to check in (US engineers weren't allowed to check in code.) ...usually it's the other way around. May I ask what the situation was? Reverse-outsourcing by the Indian central government?

Not OP. Sounds like he was considered to be a manager and wasn't allowed to get into the weeds. So instead of just managing the off shore team, he wrote some of the code for them and then let them take credit for it.

Yes and No. My job title was "Software Engineer," though my management chain told me my role was "Product Owner." Agile was fine at the beginning when it was a few people who knew what they were doing, but it's become a load of horse-shit.

The issue was that my management chain was concerned that my time was too valuable to be spent writing code. And there's a yes-and-no in this one. I was a reasonably well paid US-based software engineer, so yes, my time was valuable. And yes, some of the non-coding tasks I performed were probably more impactful than writing code. But... code + machine parsable specifications + docs + tests are very good ways of communicating exactly what you want.

I'm just sort of laughing thinking about what my old management chain would think if they knew our India based devs and I were using TLA+ as the core of our specification / documentation. Actually, I doubt they would understand it.

Re: NASA Force

#343

Post by OhMeadhbh » Thu, Apr 23, 2026, 7:11 PM UTC

gremlinunderway wrote: post #311

jimmydddd wrote: post #180

Earlier quoted context omitted.

Not OP. Sounds like he was considered to be a manager and wasn't allowed to get into the weeds. So instead of just managing the off shore team, he wrote some of the code for them and then let them take credit for it.

Which also means that he wasn't doing his job (management) and instead micromanaging his staff by doing their job. This is such a common problem with highly technical managers because they can't seem to understand how to change focus or scope and do their jobs better. Instead they fall back on trying to ship features thinking that this is productive and to pat themselves on the back for staying technical.

I was not a manager. I was hired as a software engineer.