Re: Embarrassing
There used to be a time (around 20 years ago) when people would gather to talk about the latest and greatest of both software and hardware and dream what could be done next without worrying about things being broken as much as we see nowadays with people worrying if the next update will make their pcs unusable...
In the old days, one would apply an update happily thinking it would improve security or make programs more stable... 20 years later and instead of having a rock-solid (remember when that was a cliche for windows 2000 or NT?) we endure low quality programming... This has become a trend not only in MS but in a lot of companies like Symantec, Oracle, etc, where they can't keep up with their own developers and rushing unfinished stuff out. I have read how games feel unfinished or needed polishing, but there is the saying, can you polish turds?
The need to release new things in order to stay afloat in the market is what drives companies to release unfinished products, but then, mistakes like forgetting to include a package into the build, really shows how tangled their processes have become, they can't or didn't develop a check program/list of what needs to be included in a patch. That is just amazingly disappointing.
Imagine what companies developing software for MS are building on top of (a terrible and unstable platform, where core functionality just breaks because of an update) and what their products are going to perform.
I read about people just giving up on information technology and losing faith in what can be done, even laughing at MS going down in flames, but it shows how we embraced blindingly the trends and didn't care enough to put a stop on fast development and focus on stuff that works and keeps working from the start.
Biting the hand that feeds IT
