2008 - Age of Awakening / 2016 - Age of disclosures / 2021 - Age of Making Choices & Separation / Next Stage - Age of Reconnection and Transition! /
2024 - Two millenia-old Rational Collectivist societal cycle gives way to the Self-Empowered Individualism. /
2025 Golden Age begins
Showing posts with label microsoft. Show all posts
Showing posts with label microsoft. Show all posts

Friday, August 30, 2013

Why is Microsoft really doomed?

.
Why are Microsoft and similar large organisations really doomed to fail?

Bad CEO?  Don't think so!

-  It's the system!   - Because of the systemic handicap inherent in large collectives!

Because it is more advantageous for middle ranking management to compete internally undermining their colleagues' departments and project developments, rather than make their company compete on the market!

Undermining a corporate colleague is more career-rewarding, for a "monkey", and brings rewards faster than a successful project management! It is a culture of hierarchical collectivism where a stronger must fight a weaker and must suck up to the higher in ranks. It is a culture of punishing the one who tries to work for a slightest mistake while rewarding her  boss for all successes. It is a culture akin of a herd of primates where everybody is a follower, nobody is capable or willing to show any creativity, and everyone spends all energy on social interaction and power games.

Eventually, normal humans are treated as misfits and leave or are pushed out, and those who embrace that culture, or are of this culture - stay in.

See the article:

“Microsoft’s Lost Decade” by Kurt Eichenwald
http://www.vanityfair.com/business/2012/08/microsoft-lost-mojo-steve-ballmer

Quotes (from Kurt Eichenwald's article):

The story of Microsoft’s lost decade could serve as a business-school case study on the pitfalls of success. For what began as a lean competition machine led by young visionaries of unparalleled talent has mutated into something bloated and bureaucracy-laden, with an internal culture that unintentionally rewards managers who strangle innovative ideas that might threaten the established order of things.
...
Fiefdoms had taken root, and a mastery of internal politics emerged as key to career success. In those years Microsoft had stepped up its efforts to cripple competitors, but—because of a series of astonishingly foolish management decisions—the competitors being crippled were often co-workers at Microsoft, instead of other companies. Staffers were rewarded not just for doing well but for making sure that their colleagues failed. As a result, the company was consumed by an endless series of internal knife fights. Potential market-busting businesses—such as e-book and smartphone technology—were killed, derailed, or delayed amid bickering and power plays. That is the portrait of Microsoft depicted in interviews with dozens of current and former executives, as well as in thousands of pages of internal documents and legal records.

...

More employees seeking management slots led to more managers, more managers led to more meetings, more meetings led to more memos, and more red tape led to less innovation. Everything, one executive said, advanced at a snail’s pace. “There was this institutionalized system, and it was like designing software by committee,” said Prasanna Sankaranarayanan, a former Microsoft engineer. “Things moved too slowly. There were too many meetings.” Just as with e-books, opportunities for major product developments slipped away. …
By 2002 the by-product of bureaucracy—brutal corporate politics—had reared its head at Microsoft. And, current and former executives said, each year the intensity and destructiveness of the game playing grew worse as employees struggled to beat out their co-workers for promotions, bonuses, or just survival.
...

Death by "stack ranking" peer-review system.

Quotes:


Microsoft’s managers, intentionally or not, pumped up the volume on the viciousness. What emerged—when combined with the bitterness about financial disparities among employees, the slow pace of development, and the power of the Windows and Office divisions to kill innovation—was a toxic stew of internal antagonism and warfare.

“If you don’t play the politics, it’s management by character assassination,” said Turkel.

At the center of the cultural problems was a management system called “stack ranking.” Every current and former Microsoft employee I interviewed—every one—cited stack ranking as the most destructive process inside of Microsoft, something that drove out untold numbers of employees. The system—also referred to as “the performance model,” “the bell curve,” or just “the employee review”—has, with certain variations over the years, worked like this: every unit was forced to declare a certain percentage of employees as top performers, then good performers, then average, then below average, then poor.

“If you were on a team of 10 people, you walked in the first day knowing that, no matter how good everyone was, two people were going to get a great review, seven were going to get mediocre reviews, and one was going to get a terrible review,” said a former software developer. “It leads to employees focusing on competing with each other rather than competing with other companies.”

...
“I was told in almost every review that the political game was always important for my career development,” said Brian Cody, a former Microsoft engineer. “It was always much more on ‘Let’s work on the political game’ than on improving my actual performance.”

Creating wealth versus selling someone's product.

Quotes:

In Walter Isaacson’s authorized biography Steve Jobs, Jobs acknowledged Ballmer’s role in Microsoft’s problems: “The company starts valuing the great salesmen, because they’re the ones who can move the needle on revenues, not the product engineers and designers. So the salespeople end up running the company.… [Then] the product guys don’t matter so much, and a lot of them just turn off. It happened at Apple when [John] Sculley came in, which was my fault, and it happened when Ballmer took over at Microsoft. Apple was lucky and it rebounded, but I don’t think anything will change at Microsoft as long as Ballmer is running it.”

Most interesting, however, is that Jobs put the ultimate blame on Bill Gates: “They were never as ambitious product-wise as they should have been. Bill likes to portray himself as a man of the product, but he’s really not. He’s a businessperson. Winning business was more important than making great products. Microsoft never had the humanities and liberal arts in its DNA.”

Another potentially big issue, from a very different point of view:
A dialogue between the Market Diva and myself




Saturday, August 6, 2011

Warning MS C++ 2010 runtime upgrade breaks ATI graphics drivers! (off-topic)

.
I appologise for this quick off-topic warning post, but this info might save many of you from throwing out a perfectly good ATI Radeon 4xxx series that suddenly stopped working.  I use ATI HD4670 in Win7 32bit, but this may apply also to other series of ATI cards.

A very recent upgrade of Microsoft C++ run-time library version 2011.0.30xx to 2011.0.40xx (Win7 32bit) breaks ATI Radeon graphics drivers. The symptoms are similar to when a graphic card breaks due to a hardware failure, that is screen goes suddenly black during a boot up, in high resolution large screen mode, while it may still be working when booted in the "safe mode".

I haven't tracked down yet where that .40 upgrade came from but I have determined it by multiple trial and errors beyond reasonable doubt that it is caused by the Windows 7 system run-time library incompatibility.

To fix the problem:

1) If your screen is already black, shut down, remove ATI Radeon graphics card, plug in some other card (Nvidia or something much older, even a standard VGA will do). Reboot.

2) Open Control Panel, Programs and Features - Check if you have MS C++ 2010.0.40xx Run-time installed. If yes then uninstall it.

3) Go to www.amd.com go to ATI Radeon downloads section, download and install "ATI Catalyst Center" (this will install all necessary graphics drivers for the ATI Radeon series) . I installed an older version (10.12) but the most recent one (11.7) should also work They all install MS C++ 2010.0.30 run-time library, as part of their overall installation process - verify the log that it was installed OK! If you forgot to uninstall version 40 then this step of "ATI Catalyst" installation will report a failure!

4) Shut down the PC, remove the old graphics card, reinstall ATI Radeon, restart.
.

Sunday, October 25, 2009

Will C++ destroy Microsoft Corp.?


The last 2 weeks of struggle to install my wife's "Simply Accounting 2008 Premium Student's Ed." (SA) by Sage, on Windows XP convinced me that the answer has to be positive.

Problem.

The package installer program would crash at the end of installation. Event Log showed that the crashes were due to a missing class, message issued by CLR module from the .NET2 framework. Turns out SA was compiled using Visual Studio 2005 and uses .NET2 but some changes after 2005 (most likely .NET3.5 or some service packs) broke the compatibility. It's not just one application problem. Apparently, the same happens to Microsoft SQL Server 2005 on a fully upgraded and fully service-packed WinXP Pro. It hangs or crash on install, except when installed on a fresh un-upgraded WinXP.

Solution.

Think about Linux then uninstall in this order: .NET3.5, .NET3.0, then .net-sp2, then unistall .NET2 . If uninstallation fails at any of the stage use dotnetfx_cleanup_tool.zip (from Microsoft web site). Get rid of all .NET down to .Net1.1. Turn off automatic upgrades. Re-install .NET2 using dotnetfx_Net2.exe from Microsoft web site. Reboot. Reinstall application program. Think about Linux again.

Conclusions.

1. .NET framework issued with Visual Studio 2008 appears to break old applications that use .NET2.

2. With C++ being Microsoft's language of choice, .NET framework was introduced by Microsoft to overcome C++ inherent flaw - it's inter-modular binary incompatibility. Clearly that does not seem to be working very well. However C++ does work very well for Linux/Unix OS where applications are distributed as sources and binary incompatibility does not matter! In short: C++ + GPL = sucess, C++ + $$$ = failure!

3. Microsoft is probably not using .NET for it's own new applications, so shouldn't we either!

Microsoft used to tout like crazy ASP.NET and all .NETx.x plus a small herd of other impossible to remember acronyms like WPF etc, from every media outlet. I believe that they may have already quietly scrapped all that new Application Programming Interface garbage! Ever tried installing Internet Explorer 8 without the latest .NET3_3.5? It works like a charm, no problem! I wonder what was the truth behind the rumors of their Vista development "Reset" (code scrap & re-write) in 2005? Is that only my nagging heretical suspicion that it may have had something to do with a hypothetical major flaw in their .NET framework?

4. I have seen the future and it might just work... My view on Objective-C and C++

5. Think about Linux...

6. Why do I think that C++ is an upside-down language...
.