It seems that the larger an organization becomes, the less it is able to coordinate it’s activities and falls under the ”left hand not knowing what the right hand is doing” syndrome. This is certainly the case with Microsoft in recent years. The world’s largest software company seems to be teetering under it’s own massive weight, unable to create working software without massive piles of bugs–along with leaves, dirt, rodent droppings, twigs, and rusty scrap metal.
Okay, I messed up the analogy, but I’m trying to be reasonable when I really just want to call up someone at Microsoft and scream at them for five minutes. But if I were to do that, some poor fellow with a funky accent in New Delhi will have to visit his or her Hindu temple at the end of the day to expunge all of the negativity I bestowed upon them, since I’ll never get to actually speak with anyone at Microsoft.
So what’s the problem–what’s with all the honking? I’m exasperated with Microsoft’s software. I’m experiencing stress headaches and hypertension because the hassles of modern software development just won’t let up. Everywhere I turn, it’s another service pack or security update or release candidate or beta test. When software is actually released (let the marketing goons go on the offensive!) does it work out of the box? Occasionally. Sometimes. As long as you don’t allow Windows Update to actually run, then download some new service pack or patch or band-aid or splint, and install it on your hapless PC, thus rendering it only forward compatible from that day hence with most of your existing software.
Microsoft is, in day-to-day operation, behaving like a schizophrenic with ADHD–experiencing conversations with imagined people, while getting on their nerves with hyperactivity, all the while completely ignoring the real world. That’s Microsoft in a nutshell trying to keep 50,000 programmers and other members of the peonic elite busy on a daily basis. All of that momentum, keeping the ship moving, without remembering the destination…
I remember a time when Microsoft created good software. It was a longggg time ago, back in the dark ages for most young people, but a lot of those in my generation who recall the early days of the PC industry will recall a day when quality was more important than quantity because software companies at that time operated on a different premise: Not that 50,000 programmers must be kept busy churning out garbage year after year, but that a few dozen or a few hundred programmers worked hard on a software package either to unleash it on the PC industry for the first time, or to update a beloved application with user-requested features and productivity improvements. Today, Microsoft is so monstrously off it’s rocker it’s own software development teams are not even communicating needs to each other and ensuring that software packages are designed to work together.
A few years ago, back in 2004, I complained quite a bit that Microsoft was abandoning a long-held tradition of providing backwards compatibility in it’s software. Each new version of MS-DOS was supposed to support all previous software built for prior versions of MS-DOS. So, as a developer working on an application for MS-DOS 3.0, you could count on it still running under MS-DOS 5.0. And that is exactly how things worked back then. In the 1990s, Microsoft worked very hard to make sure 16-bit Windows 3 applications would still run under the new Windows 95 operating system. That was a huge concern in the PC industry.
Read more on linky... (Fifth article down, titled (Windows, again killing backwards compatibility)
Bookmarks