I agree with you what you are saying about string localization.
Separately, I find that people tend to assume (for some reason?) that big successful companies that write lots of software will also write quality software. They have the money for it!
But its often not the case. Look at Microsoft in the late 90s.
Look at Apple these past few years.
Maybe the people at the top sometimes feel they no longer _need_ to write quality software, because they are at the top?
The goto fail bug is a singular mistake, but I'm not convinced it was an isolated mistake. I've worked with teams of amateurs that had code quality practices sufficient to prevent such a bug; and yet apple included this in a product, and left it there for a long time before it was fixed. It suggests, to me, organizational issues.
Separately, I find that people tend to assume (for some reason?) that big successful companies that write lots of software will also write quality software. They have the money for it!
But its often not the case. Look at Microsoft in the late 90s.
Look at Apple these past few years.
Maybe the people at the top sometimes feel they no longer _need_ to write quality software, because they are at the top?
The goto fail bug is a singular mistake, but I'm not convinced it was an isolated mistake. I've worked with teams of amateurs that had code quality practices sufficient to prevent such a bug; and yet apple included this in a product, and left it there for a long time before it was fixed. It suggests, to me, organizational issues.