I'm not in that industry anymore but I just wish everybody would just grow up, use this (and related) software and contribute. No reason not to do that (of course except for pride).
I'm not in that industry anymore but I just wish everybody would just grow up, use this (and related) software and contribute. No reason not to do that (of course except for pride).
Obviously there can be situations where common approaches are developed and used but this seems to be the exception rather than the norm.
(source - I've spent 10 years trying to work this issue in a UK public acquisition context)
The first maximizes "unique requirements" while the second minimizes them.
Between the two, I generally prefer "build", bad as it is, because it leads to fewer horror shows later.
(10 years at MSFC, 28 years in this industry.)
Maybe you mean that every manager creates a distinct AWS account for their own department? That would be fairly irregular but possible.
Naturally no one was willing to give up on their own one.
It's the same in automotive industry (development and end-of-line-testing) (XCP and MDF helped, but ultimately devolved into a meta-standard for vendor specific functions) and in the rest of the industry I've had contact with (cooling, heating), fragmentation is as bad as ever.
Standardizing on web standards will probably follow the pattern of making of adding another layer that is worse than anything in the previous 30 years.
:(
Heh, sounds like they have a lot in common with JavaScript frameworks and web development in general. With this observation in mind I doubt making mission control "web based" will rectify the situation...
I do not know the details of mission control technology but my uneducated guess would be that this is a cultural/management problem in these organizations. Top-down hierarchy with very large resistance to change would make introducing of new ideas (open source solution in this case) a tough job for any single actor. Also the IT-contractors or companies benefitting from selling these solutions are probably doing everything they can to keep the status quo as it is.
How much time do you lose keeping track of those solutions and their dependencies?
The JS world has probably the hugest fragmentation problem in software history. Every level in the stack is rapidly evolving, constantly spawning multiple half-baked alternative solutions to the same problems. I think GP's point is simply that if similar things are happening in NASA on small level and are considered a problem, then switching to a technology ecosystem that is a living embodiment of those issues isn't going to help.