3 ms·
As I wrote when this showed up on proggit, Not to put too fine a point on it, but I would be very skeptical about using NASA as a good example for much of anyt
by mcguire 9y ago
As I wrote when this showed up on proggit,
Not to put too fine a point on it, but I would be very skeptical about using NASA as a good example for much of anything, but especially software development.
My bonifides: I'm 49; have spent roughly 25 years as a systems programmer, systems administrator, and general bit wrangler; and I worked for 8 years at the Marshall Space Flight Center, specifically the NASA Enterprise Application Competency Center.^1 (And yes, that's a thing. Started as IFMP (Integrated(?) Financial Management(?) Program), and was IEMP (Integrated(?) Enterprise Management(?) Program) when I started.) If you're a NASA employee, you might recognize STaRs (I worked on the rewrite, post Perl 1 and Monster.com), NPROP/Equipment, or DSPL/Disposal. And IdMAX, which I noped out of shortly after moving to the project.^2
NASA itself is a massively disfunctional organization, in my experience, and a failure to "cut through the bullshit" is a major reason why. For software development specifically, while I didn't do anything with "man-rated" development or the other important bits, I have strong doubts that they are any better than other avionics, automotive, or other embedded development organizations.
There was no mentoring. People tried, it didn't go over well, usually with the mentees.
You have to trust each other's potential, because there is no damn chance of getting any two projects to agree on anything. What goes on in that other silo is their business, not yours.
I did say, "I don't understand." A lot. Frequently pronounced "WTF?"
The list of "unreliable sources of knowledge" looks rather like a checklist of how things got done.
^1 NEACC is also the acronym for the North-East Alabama Community College, which I find ironic for no good reason.
^2 Unfortunately, I don't have a picture of me looking arrogant. Sorry.
- throwaway12017 9y agoI will copy and paste my reply from your last thread: NASA, like many large organizations known for prestigious accomplishments, can struggle to meet the needs of those doing the enterprise work (like internal HR apps as you mentioned). Especially in a place like the government, people's ego's feel small, and they try to compensate by making their projects bigger, grander, and overstated. This just results in bloat, too much talking, and BS as you mentioned. I'm sorry you had that experience. If you ever consider coming back, I'd recommend getting involved with something more directly related to space applications.
- deleted 9y ago[deleted]
- lisper 9y ago> NASA itself is a massively disfunctional organization, in my experience, and a failure to "cut through the bullshit" is a major reason why. I completely agree with this, though I think it's important to note two things. First, despite the dysfunction, they do, more often than not, make things that work under extremely challenging conditions. And second, a lot of the dysfunction is not their fault, but is a consequence of the fact that they are a government agency and hence ultimately answerable to Congress. Not only that, but they are a government agency created to fight a (cold) war that ended almost thirty years ago so they have been rudderless for a long time. The fact that they've done anything other than suck up taxpayer dollars is a testament to the incredible skill, both technical and political, of many of the people in the agency. Notwithstanding my vocal criticism of the organization, I have tremendous respect for many of the people who work there.
- hindsightbias 9y agoI never knew what code post-80's NASA regulars actually wrote. When the MCC was moved off of the mainframe (MOC), it was all contractors. A crazy mix of skillsets in C/C++. A lot of subsystems/silos. Working across silos, it was incredible the brain trust you could meet from the old crowd (often retirees brought in for 2AM tests). I learned a lot of kids were afraid to say wtf. These old coots would love to talk for hours if you asked why something was done that way. Considering the TRAJ assembly probably went back to DEW Line, I have no idea how they peeled that logic off. I still run into LockMart folks running ancient ATC code on Unix variants that have been out of service for over a decade. Our code will never last that long.