Ayende @ Rahien

Hi!
My name is Oren Eini
Founder of Hibernating Rhinos LTD and RavenDB.
You can reach me by phone or email:

ayende@ayende.com

+972 52-548-6969

, @ Q c

Posts: 6,124 | Comments: 45,470

filter by tags archive

No one was fired because they bought Microsoft

time to read 1 min | 102 words

And just to be clear, I don't agree with this sentiment, but it is a very real one.

Times have changed
Our applications are getting worse
They run so slow and won't behave
The code is ugly and perverse!
I tell you, that application is deprave!

Should we blame the PM?
Or blame the developers?
Or should we blame the process?
No! blame Microsoft
Everyone: Blame Microsoft

Blamability is an important concept, the facts doesn't really matter, but the ability to blame someone else, preferably something as ambiguous as Microsoft, is a good way to have an out.


Comments

Diego Guidi

Looks like a modification of a medley of South Park - The Movie... blame Canada!!! :D

Chris May

I don't think the "No one was ever fired because they bought Microsoft" has to do with the ability to turn around and blame Microsoft if things don't work right.

I think it is because Microsoft is in many ways a defacto selection for most software products.

If you are buying an office product, you are going to buy Microsoft Office for your company.

If you decide to pick something other than MS Office, it is your butt on the line if things don't work.

if you install OpenOffice.org and it crashes when the President is in the middle of a big presentation, you are going to have to explain why you picked the lesser know office option. In other words, why did you pick an option than only 2-3% of the world thinks is the right solution.

If you picked MS Office and it crashed, no one is going to question why you were so stupid as to buy the office product that 95% of business users rely on.

Same goes for the OS. The CEO isn't going to be pissed off at the CIO because he can't figure out XP Pro, but if you installed Ubuntu, then you have some explaining to do.

Comment preview

Comments have been closed on this topic.

FUTURE POSTS

  1. RavenDB 3.5 whirl wind tour: You want all the data, you can’t handle all the data - 2 days from now
  2. The design of RavenDB 4.0: Making Lucene reliable - 3 days from now
  3. RavenDB 3.5 whirl wind tour: I’ll find who is taking my I/O bandwidth and they SHALL pay - 4 days from now
  4. The design of RavenDB 4.0: Physically segregating collections - 5 days from now
  5. RavenDB 3.5 Whirlwind tour: I need to be free to explore my data - 6 days from now

And 14 more posts are pending...

There are posts all the way to May 30, 2016

RECENT SERIES

  1. RavenDB 3.5 whirl wind tour (14):
    29 Apr 2016 - A large cluster goes into a bar and order N^2 drinks
  2. The design of RavenDB 4.0 (13):
    28 Apr 2016 - The implications of the blittable format
  3. Tasks for the new comer (2):
    15 Apr 2016 - Quartz.NET with RavenDB
  4. Code through the looking glass (5):
    18 Mar 2016 - And a linear search to rule them
  5. Find the bug (8):
    29 Feb 2016 - When you can't rely on your own identity
View all series

RECENT COMMENTS

Syndication

Main feed Feed Stats
Comments feed   Comments Feed Stats