3 ms·
Isn't the main reason just that failures in the vast majority of software aren't that bad? Like if you build a bad house it could collapse and kill someone. If
by p1necone 4y ago
Isn't the main reason just that failures in the vast majority of software aren't that bad? Like if you build a bad house it could collapse and kill someone. If you build a bad calendar app/email client/text editor it might... be a bit difficult to use? Crash sometimes?
And then people wont use it because it's bad and your company will go under, problem solved. Some other 20 year old (or 40 year old) flying by the seat of their pants who happens to be good at development will step in and build something that works.
Obviously if you're building medical device firmware, or aircraft control systems or whatever then it's a whole different story. But generally companies building that sort of thing do have a much more systematic and dedicated approach to quality. And there are industry regulations that enforce that.
- tintor 4y agoIf you build a bad email / calendar app user emails and meeting info might leak, and cause harm.
- nazka 4y agoAnd still there are so many leak of personal infos and startup X having been hacked and Y millions of data about personal infos and account infos being leak in the dark web. But like nobody really care. It does a few articles in tech news and some tweets and that’s it. (Now I’m not saying that I don’t think it’s bad but the millions of people around me don’t think it is)
- eastbound 4y agoSeniority doesn’t change a lot here: - Sure, a senior might not use that NPM package coming from Zorglub89 on the internet, but then they’ll also execute slowly because of the hurdles of checking for these packages. - Sure, a senior will perform external security audits regularly, but a lot of seniors are also in it for money or career and will be rogue. IT has systemic leakage of PII.