4 ms·
+1 for systems engineering. Sadly it isn't more common in software development.
by cardosof 5y ago
+1 for systems engineering.
Sadly it isn't more common in software development.
- da_chicken 5y agoIt 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.
- jacquesm 5y agoIndeed. I see this as our downfall: if the price of failure drops then failure becomes commonplace.
- fullstackchris 5y agoThat'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.
- flyyingbarron 5y ago+1 for systems engineering indeed. 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. If you're interested, my first article can be found at : https://medium.com/ibm-garage/out-of-this-world-lessons-from-the-apollo-lunar-landings-part-i-703ff4f872ce https://medium.com/ibm-garage/out-of-this-world-lessons-from...
- waiseristy 5y agoSystems engineering roles are typically considers lesser / lower skilled than software roles as well. Which is absolutely ridiculous
- ncmncm 5y agoIf programmers were held to standards routinely upheld by systems engineer, software would not be such crap. There would also be less of it, which would be another boon.