One of the most entertaining reads as of late has been the blog of one Mini-Microsoft: A well-written anonymous Microsoft insider with an axe to grind about the way the company is being run, and with some disagreements about the direction the company is headed. "Let's slim down Microsoft into a lean, mean, efficient customer pleasing profit making machine! Mini-Microsoft, Mini-Microsoft, lean-and-mean!" he petitions from the front page.

 

Mini's position isn't novel in the world of corporate worker bees. Malcontent about one's workplace, one's superiors, and compensation is close to a universal gripe. What makes Mini's rantings interesting, aside from the often humorous writing, is that it emanates from a company long considered the exception - the company that defied all of the normal rules of corporate culture. Microsoft was the one organization, we heard, where you didn't have the traditional stratification between the lordly executive - forever blameless and masking incompetence through endless restructurings - and the lowly drones that were treated as replaceable cogs. Microsoft’s developer culture, where the productive intelligent developer was king in the quest to make the best software products, was the benchmark towards which every .COM dreamer aspired when they laid out their plans for world conquest. Microsoft was the “It” employer that Google has become.  

 

Of course as organizations mature they sometimes evolve in ways that aren't compatible with some of their employees. When that happens, pretty much inevitably over an organization’s lifespan, the disgruntled will often take to the airwaves (blogwaves?) to air their grievances, grouching and griping to all who’ll listen about how great things used to be, and how things should be done if management weren’t such idiots. While they might eventually adapt, or the organization might change to accommodate them, the disaffected are far more likely to eventually move on. That sort of transition is inevitable, and as no-one should consider an employer/employee relationship a lifetime commitment, it shouldn’t come as that much of a shock.

 

Having said that I don’t think that’s the case here and it really sets Mini’s blog apart from the endless reams of ex-BigCorporation employees publicly airing their historic dirty laundry. Mini has not only earned the admiration and support of a lot of Microsoft faithful, but his position is empirically supported by Microsoft’s underperformance as of late. No doubt Microsoft does have a serious problem, and is truly an organization in crisis. Perhaps the impression will change after a cluster of long overdue products are released over the next 16 months, but it certainly is the impression today.

 

The roots of the problems are obviously varied for such a large organization, but it is nonetheless enjoyable to armchair theorize. I was given the opportunity a short while back while I was speaking with a Microsoft rep. I was asked what I thought Microsoft’s #1 problem was (must be on the call sheet question list or something). My reply was simply integration – Microsoft is so dedicated to integrating all of their products and technologies starting at v1.0, tying and cross-integrating, that the speed of development slowed to a crawl. One doesn't have to work at Microsoft to understand the threat this presents. Suddenly every delivery slip suddenly affected dozens of products, and every technology risk took on a vastly increased role. The critical dependencies between projects because pervasive, and communication channels to design and deliver products and technologies increased exponentially.

 

Couple this with the fact that the upper-level of Microsoft has become so paranoid about their dependency on platform monopolies that they are seemingly incapable of letting their incredibly capable development teams solve problems in the most effective manner. Microsoft is, for reasons I discussed previously, by far its own biggest competitor, so everything any team does you can be sure had to be approved and agreed upon based upon the strategic interest of the status quo (in particular the Office and Windows hegemony). It wasn't surprizing, for instance, when the powers that be at Microsoft reigned in the hugely successful Internet Explo

Just saw a post on a Microsoft evangelist's blog that reminded me (however tangentially) of something that I've oft mulled over - bias, both conscious and subconscious, and how it manipulates the things we say and the image we try to present to the world (and conversely the image the world sees when they look at us, which leads the cynical reader be to cry "Hidden Agenda!" in response to seemingly innocent posts).

To draw from example, I was long a resident of a particularly cliquish online community - one where pretty much all of the members were software developers (or working in related disciplines). We'd often argue about industry trends and technologies, debate the merits of various nefarious corporations, and so on. Good conversation, and I gained a lot of wisdom and knowledge from the often heated exchanges. I also got to see one particularly good example of bias, both real and perceived, on the exchange of information.

It began when one of the more moderate, well-spoken, and respected members - someone whose voice carried great weight by a long history of wisdom, and whose real identity was unknown to most - announced that he had been hired by a new employer. An employer who he would reveal shortly after the details firmed up. I emailed him my guess, and learned that I was right: The new employer was Microsoft.

I believed that I knew who their new employer was by the marked shift in bias he showed towards Microsoft in the prior two weeks (while the offer was firming up): Suddenly, it seemed, this individual was more accepting of historical Microsoft practices, more derogatory towards Google, more disparaging towards web application, and had an increased preference for fat clients. Lots of people entirely unassociated with Microsoft hold these sorts of positions, but it was the change in position that was so notable to me. Maybe it was just a lucky guess and I was just imagining a change in position: To this day the person in question claims that their persona and positions didn't change. I actually believe them, in that I believe that they didn't intentionally or knowingly change their opinions, but their new alignment towards Microsoft most certainly did have an impact at a subconscious level, gently pushing their opinions in favour of Microsoft.

In any case, once this person's new employer became public knowledge in the community, they found that their input on technology matters was often dismissed by cynics as having no credible value. To a small degree the cynics were right - It was impossible, short of some sort of hypnosis, for this newly minted Microsoft employee to weigh in on matters that in any way concerned Microsoft's interests without consciously worrying about someone at Corporate Headquarters seeing their comment and it hurting (or alternately failing to help) their career, or on a deeper, more insidious level - their subconscious - feeling the need to offer up goodness towards Microsoft in kind for a paycheck.

Of course this sort of bias doesn't even require you to be an employee. One of the most difficult to stomach personalities in this industry is the Desperate-To-Be-A-Microsoft-Employee. This sort of person is driven to fight for Microsoft to the ends of the Earth, to clumsily adopt and champion every bowel movement Microsoft squeezes out, and to coddle up to every appendage of Microsoft (Scoble has a lot of these fawning admirers. He also has a lot of well-deserved admirers, but if you ever witness a thread where someone criticizes Scoble, watch for the sacrificial Scoble defenders to ooze out of the DIV tags, desperately hoping that someone at the Microsoft collective writes down their name and sends them an offer). These people, falling back to basic human psychology, at least subconsciously believe that if they send sweet love Microsoft's way then they'll get some in return, and the result is messy for everyone.

Even if you aren't a Microsoft employee, and you have no interest in ever being one (for me it really isn't an option, as the Canadian operation is almost entirely sales, or pseudo-sales, and I plan on staying in this country outside of an extraordinary opportunity), if you've invested a lot of time and effort into the Windows platform then you will still likely have a bias to defend the platform, and to deride threats to it. Earlier in my career, perhaps when I had a more narrow range of skills, I found myself falling prey to exactly this motivation quite a few times. I felt it necessary to defend Microsoft and attack its competitors in some sort of perverted belief that I was helping to maintain the status quo, ensuring that my knowledge and status weren't being threatened. You can see this sort of status quo bias all the time, with the mainframe guys deriding desktops, DB2 guys endlessly (and falsely) criticizing SQL Server, and so on. A lot of the noise masquerading as debates out there are founded on this motivation, just as most of the political grandstanding following Hurricane Katrina was partisan, biased noise, with every participant taking exactly the position one could have predicted months before.

While I've picked on Microsoft a lot, it just happens to be one of the easier examples, but the same sort of forces exist in a lot of spheres. For instance the tech world is awash with Google-Love right now, with every hopeful Google candidate flooding the boards with pro-Google rhetoric at every chance. While Google is undoubtedly a technical superstar that is executing ideas absolutely brilliantly, it is remarkable seeing such admiration for what is essentially an internet advertising company. Where was the love for DoubleClick?

The point that I'm trying to make in this rashly authored entry is quite simply that bias is enormously pervasive, and should never be underestimated. It drives almost everything we "believe" and say. It is often a destructive noise that thwarts rational and critical analysis and thought.

A peer was commenting about open offices (e.g. large areas with several work areas) versus cubicles, and what the advantages/disadvantages of each holds for software development. While this is painfully obvious, it suddenly struck me that cubicles allow you to jam people even closer together - without the barriers of partition walls, natural psychological "bubbles" would prevent one from packing employees as closely. Put a little superficial wall and you can jam people right up beside and afront each other, within arms reach in many cases.

I've worked in both (RBC, in particular, had an absolutely terrible work environment for all but senior management. Tiny little micro-cubicals about 4 feet deep with your back against heavily trafficked corridors: Combine the worst of both cubicles and open offices. Add in the sleep inducing din of the AC, overlaid with the rhythmic tapping of hundreds of people pecking away at their keyboard filling out their TPS Reports, and you have a creativeless, life-sucking environment where the intelligent part of your brain goes to die), along with of course private offices, and I definitely prefer the former if a private office isn't possible.

While I'm currently a Mozilla Firefox user, I was a very satisfied user of Opera for some time, enjoying some of its superbly implemented innovations such as mouse gestures. The "downside" of Opera, and a large impediment to its adoption, was the browser-embedded banner ads if you didn't purchase a registration key (which few did, as relates back to a prior entry where I observed that the only widespread competitors to Microsoft on the Windows desktop are free-as-in-beer software. Opera costed a marginal amount of money, so like many other pieces of software in that situation it remained a fringe application despite its many competitive advantages).

Opera has apparently finally tossed in the towel in its quest to sell their application on its ample merit (check out the feature sheet - native SVG rendering, super fast and lightweight, highly standards compliant, integrated RSS - This is a top notch browser), and is now offering their superb browser for free, downloadable here. Presumably they're moving to more "modern" revenue techniques like pay support, and perhaps partner agreements.

Even if you don't make it your primary browser, you simply must give it a try on your favourite websites and evaluate it on merit. At the very least ensure that sites you develop work properly in Opera as well.

[Slashdot has a discussion regarding this. Additionally I should note that if Opera sees widespread adoption, which I highly doubt given the lack of competitive application "shopping" among the Windows userbase, it may prove my SVG is dead claim wrong]

A comment on a message board I occasionally visit (a comment in which a poster asked what the most popular commercial non-Microsoft software for Windows was) made me revisit some thoughts I have often mulled about: The Windows platform, originally envisioned as a multi-vendor foundation on which a rich ecosystem of best-of-breed software would interoperate in this standardized GUI environment, has in many cases turned into a Microsoft-only affair, often customized with at most a couple of internal, proprietary apps.

This is an obvious observation that many have been "warning" about for years (over a decade, really), but it really is profound when you stop and really think about it. Personally I know that my average day is almost entirely filled with Microsoft Visual Studio, Microsoft Office, Microsoft SQL Server, all on my Microsoft Windows 2003 operating system, with additional services provided by Microsoft Windows Servers and Microsoft Exchange. I hardly think I'm an exception.

Some of the last bastions of widely distributed commercial alternatives, firewalls and anti-virus, have both been brought in-house as well, and soon enough will be a part of the platform. Niche markets, like high end image-editing, are also being competently assaulted by Microsoft, and even Macromedia Flash is coming under assault in coming months. Microsoft has had considerable success in the entertainment (games) market, but even then is working to usurp the Microsoft Windows gaming crowd with hardware like the XBox 360.

Of course Microsoft does see some competition, such as the fantastic success of Firefox (which accounts for almost 40% of the visitors here), but it is almost entirely from free software (with an emphasis on the free-as-in-beer element). The ranks of competing professional software companies targetting the Windows platform has whittled down enormously. It has to make ISVs nervous when faced with pages after pages of questions about their business and products when signing up for programs like Microsoft's Empower program

It just is remarkable how diverse and competitive the Windows platform once seemed, yet now we're at the point where Microsoft might as well sell tools like Office prepackaged as a "part" of the OS. Maybe a "developer" install that comes with the OS, Dev Studio, and SQL Server Dev Edition.

I pass no judgement on this or what it all means - it could very well be that these are the superior products in each of their classes, and it is simple capitalist survival of the best that brought us to where we are (most certainly an arguable point. Microsoft Office, for instance, once faced tremendous competition, but it fought on merit to the top of the heap), but it is nonetheless stunning when you compare the diversity that once existed with the largely single-vendor platform we have today.

I authored an entry this morning detailing how my PCs - which for conservation reasons I regularly turn-off/hibernate except when in use - mysteriously fail to restart whenever I really critically need them immediately. e.g. When I have to grab a piece of info before I head out the door, or I'm on the phone and need an address. In such situations, with an unbelievably high degree of correlation,  the hibernation restart will fail, or the BIOS will throw up some random error, or Windows 2003 will stall on the beginning progress bar - Something will happen that screws up the startup. I'm forced to power down on the back of the power supply (otherwise the next startup will bizarrely claim that no keyboard is attached), and then wait for the time-sucking from-scratch startup. Perhaps in such a rushed situation I hit the power button more vigorously, or in my haste I shuffle my feet on the carpet and deliver a static shock to my PC: There has to be some rational explanation for this, as my systems are flawless the other 96% of the time (when it doesn't really matter how quickly I can get at them).

It has since become apparent this information - revealing the malice and schadenfreude of our PCs - had to be suppressed. Upon trying to post this I discovered that yafla.com was down due to a RAID failure (what they really need is a RARAID). When it finally came up, after 4 hours of downtime, and the big chance came for the post to be published, Radio Userland promptly spit up a GPF and unceremoniously deleted that entry.

Coincidence? I think not...

Just noticed that I subtitled the personal category "Personal Photos and Musings". Egads, the word musings has got to be one of the most abused and overused words in the, err, blogosphere. As such I have evicted it.