3 ms·
This is a pretty silly argument. Obviously you apply different standards and methods to develop life-or-death regulating software than for customer grade game
by BurningFrog 10y ago
This is a pretty silly argument.
Obviously you apply different standards and methods to develop life-or-death regulating software than for customer grade game and web surfing platforms.
I agree that my Apple products aren't as solid as they used to be, but this would (I assume) be a very different team run in very different ways.
Sometimes I think we "anthropomorphize" companies and brand names. They're not monolithic things with one personality.
- haswell 10y agoThat's fair, and I agree that we tend to think of companies/brands in a monolithic way, but there's also an organizational component. If you look at a company and seriously question the leadership from the top down for decisions they're making related to their core business, I think we should still question whether or not they can properly assemble a "very different team". I've mentioned this in other comments: I'm not saying they can't - but they have some convincing to do.
- BurningFrog 10y agoI'm with you in that I've lost some confidence in Apple's level of quality. But not nearly to the level you're expressing.
- user5994461 10y ago> Obviously you apply different standards and methods to develop life-or-death regulating software than for customer grade game and web surfing platforms. And that's exactly why it will go badly if the average web dev is assigned to do critical software. They don't have the culture, they actually have a culture and training against it. Imagine for a second a company doing both. - In one office, there are the critical developments, where people are taught that quality matters and bug kill people. Also, you can't go back when shit is shipped, it's too late. To remind you of what "critical" means. There are people in the team, including yourself, who are still waiting for the updates on the AB957 plane crash from last month where 157 people died, because they worked on the navigation system that was in THAT plane. It's pretty sure at this point that this is not linked to the crash, but we'll be more confident of what happened after we figure out what happened. - In the next office, there are the web devs, where people are just pushed to ship more shit faster. Sometimes they say that they'll fix things later, even thought they know that they won't. They've got a list of bugs, that is mostly ignored. They know they are shipping new bugs but they don't care, they don't even try to improve the situation. Now, what's the difference between those two groups? There isn't any! All the working developers could take time for a break, sit down and have one more review before they ship :D This the hardest thing to teach to all developers: QUALITY MATTERS! It's very challenging to teach that to the average web dev because everything they know and live-in is against that. It's gonna be a problem to have an organization with tinder-like-web-development and critical development close to each other, they're too different socially and the web-culture is gonna dominate the critical-culture [Sadly, the path of mediocre-driven-development is easier than is-it-REALLY-good-enough-driven-development].