3 ms·
To be fair, NASA software engineers don't exactly act like your average agile start-up team,because once the "product" is out, patching is really feasible. Wher
by komali2 10y ago
To be fair, NASA software engineers don't exactly act like your average agile start-up team,because once the "product" is out, patching is really feasible. Whereas for your average webapp, it's more strategic to iterate based on feedback.
- Bartweiss 10y agoYep. NASA can't release patches (hardware, least) and switching to "version 2" costs a solid $800,000,000. I feel confident that if the development costs of reworking a webapp were measured in years and millions, we'd see a pretty different approach to building them.
- komali2 10y agoWhoops too late to edit. Should be "patching isn't really feasible".
- greglindahl 10y agoExcept they DO send out patches. Just not very often.
- komali2 10y agoWell, my point was it's a bit more trouble to patch something on another planet that it is to `heroku push.`
- karthikb 10y agoAnd yet, NASA frequently updates code on launched vehicles. In fact because of schedule and orbital mechanics, Spirit and Opportunity were launched before final flight code was ready, and an OTA was performed while the vehicles where in flight: http://spacenews.com/jan-15-2004-spirit-rover-begins-amazing-visit-mars/ http://spacenews.com/jan-15-2004-spirit-rover-begins-amazing...