It's unfortunate that the article speaks so much of NASA engineers and managers, but fails to mention the actual engineers that designed, built, and tested it: TRW (now Northrup Grumman) and Ball Aerospace.
> The concepts used to create the JWST are built on the same concepts used on the first satellites and space probes in the 1950s.
AKA, the field of Systems Engineering [0]. Further reading if you really want to take a deep dive [1].
Fair enough, but I felt that detailing the contractors would lengthen the article and not add to my general points.
I did mention Northrup Grumman engineers in the caption of one image.
It was when software delivery involved distribution of physical media. Now that it's all done over digital networks, people have moved to early deployment models where failure in the customer's hands is all but ubiquitous.
That's brilliant. It puts my general vibe of software basically for the past 10 years (maybe longer? for me mostly the advent of the app stores and near serial release of hundreds of thousands of apps) into a single sentance.
That's one of the reasons I write my blog - I think there are plenty of inspirational & aspirational lessons software developers (especially, but no only, in the DevOps and SRE domains) can learn from the space exploration.
Northrup Grumman is the type of company that's happy to bill the government for 3 very senior engineers to spend 4 months to rewrite a small program in a different programming language.
> The concepts used to create the JWST are built on the same concepts used on the first satellites and space probes in the 1950s.
AKA, the field of Systems Engineering [0]. Further reading if you really want to take a deep dive [1].
[0] https://en.wikipedia.org/wiki/Systems_engineering
[1] https://www.amazon.com/Mission-Analysis-Design-Technology-Li...