3 ms·

Yes, sure, but a "billion dollar company" in this case does not represent the whole industry. You can probabbly find a some specific non-critical case in aeros

Yes, sure, but a "billion dollar company" in this case does not represent the whole industry. You can probabbly find a some specific non-critical case in aerospace industry, but surely based on that example one would not suggest that the whole aerospace industry should just copy what they see in frontend dev. Context matters, there are exceptions, but the standard practices are based on average scenario, not on extremes.

thfuran 5y ago
I'm not saying that all code should be developed under standards designed for embedded control system software. I'm just saying that "oh, it's just web stuff so it can't be important" is ridiculous.
- mhaberl 5y ago
  >>> and the rest of the industry would be well advised to take notice and copy what they see >> I don't agree. >> [web form validation example] >> That is just a tradeoff, in aerospace industry you spend more to lower the risk, somewhere else you don't. > I'm just saying that "oh, it's just web stuff so it can't be important" is ridiculous. This feels like a straw man. The original argument is that the rest of the industry (that includes web, but a lot of other parts also) should copy what they see in aerospace industry. I believe that would not be appropriate for the rest of the industry to just copy practices from any other part because each segment has its own risk factors and expected development costs and with that in mind developed their own standard practices. Nowhere did I state that the "web stuff can't be important" nor that there is no example of web development (form validation) where the errors are insignificant. That said, I will go back to the "billion dollar company that can't fulfill orders" / "million people who suddenly can't use their bank online" catastrophe; this happens all the time. Billion dollar company doesn't fulfill orders, error is fixed, orders are fulfilled again, 0.0..01% of revenue is (maybe) lost. In aerospace industry a bug is deployed, people are dead. No bugfixing will matter after that moment. How can this two industries have the same standards of development?

thfuran 5y ago

I'm not saying that all code should be developed under standards designed for embedded control system software. I'm just saying that "oh, it's just web stuff so it can't be important" is ridiculous.

mhaberl 5y ago
>>> and the rest of the industry would be well advised to take notice and copy what they see >> I don't agree. >> [web form validation example] >> That is just a tradeoff, in aerospace industry you spend more to lower the risk, somewhere else you don't. > I'm just saying that "oh, it's just web stuff so it can't be important" is ridiculous. This feels like a straw man. The original argument is that the rest of the industry (that includes web, but a lot of other parts also) should copy what they see in aerospace industry. I believe that would not be appropriate for the rest of the industry to just copy practices from any other part because each segment has its own risk factors and expected development costs and with that in mind developed their own standard practices. Nowhere did I state that the "web stuff can't be important" nor that there is no example of web development (form validation) where the errors are insignificant. That said, I will go back to the "billion dollar company that can't fulfill orders" / "million people who suddenly can't use their bank online" catastrophe; this happens all the time. Billion dollar company doesn't fulfill orders, error is fixed, orders are fulfilled again, 0.0..01% of revenue is (maybe) lost. In aerospace industry a bug is deployed, people are dead. No bugfixing will matter after that moment. How can this two industries have the same standards of development?