TexBlog

Steve Teixeira's Blog -- Thoughts on parallel computing, Microsoft, the industry, and life

Survival of the Nicest… or is it the Meanest?

Survival of the Nicest… or is it the Meanest?

  • Comments 3

I’m a regular Slashdot reader.  Yes, yes, people from Microsoft do read Slashdot; it keeps us grounded to know what is on the minds of the ABM crowd.  Slashdot is often an insightful leading indicator of information technology thought and opinion.  However, every once in a while I come across a Slashdot article that I find remarkable either for it’s hater-ness or it’s naïveté.  This posting, asking whether Nice Engineers Finish Last In Tough Times, is an example of the latter.  Whether it’s sloppiness or sensationalism that allows articles like this to slip through the editorial sieve to the home page, I don’t know.  But this particular article got my goat for a number of reasons.  The first couple of reasons are pretty obvious:

  • The author obviously has pretty strong opinions about the two managers.  Is this really a case of Jim vs. Dwight battling to keep their jobs on The Office, or is there a more subtle reality being masked by the author’s opinions of the people involved?
  • I’m not a professional statistician, but I feel pretty secure in asserting that a sample size of one doesn’t meet the bar for statistical relevancy.  Does this guy’s experience with one instance of office politics really portend some sort of “nice guys finish last” trend in worldwide IT?

But here’s the thing that bugs me most about this article:

  • The article lacked any relevant data that a second-level manager would actually use to determine who kept their job.  For example, which of these two people is more effective at their job, has the most relevant experience, or judged more capable of managing the combined organization would all be important pieces of information for such a decision.  We’ve all worked with really nice people that just weren’t very good at their jobs as well as people we didn’t like that we begrudgingly admitted were effective at their jobs. 

Of course, we would all prefer to work with people that were both great at what they do as well as total sweethearts, but reality is rarely as simple as the “new trend: bad guys kick sand in face of good guys” caricature painted by this article.

  • Looking at the last VC++ releases you have to be such a sweetheart Steve :) *cough* *cough*

  • Indeed, I am a sweetheart... thank you for noticing! :)

  • I agree Steve. The appearance of today's IT environment would make you think the good guys get the boot when the bad guys seem to win, but we know looks can be deceiving.

    In the slashdot article, the “good guy” was taking the blame for things he didn't do. He was giving other people credit for things he accomplished. That's not really being a good guy, that's just a lie. The “good guy” needs to learn to give respect where respect is due, and also take a little respect when he earns it, which all is a matter of balance.

    The engineering manager is the boss, so everyone on the team should act when the manager needs action. If the “bad guy” was the one that was quickest to act, why wouldn't the manager like him, even though he's the "bad guy". Some people call that sucking up, or being a do-boy, but frankly, it's part of practically everyone's job description. Almost everyone has someone to report to.

    I think that slashdot article was written by someone who was upset that their buddy got laid off. The software world is similar to how it was before the economy when south, there are just a few added pressures that some people can't cope with in stride. The guys that are good enough to earn a pay check keep their job. The dead weights have to go, not because they are nice, mean, or a terrible combination of both, but because companies just can't afford to carry them on the payroll anymore.

    A nice guy got laid off. We'd like to think it just couldn't happen, but in this economy, it can.

    BTW

    I'm really impressed by the fact that you got almost all of my suggestions from our meeting in late 2007 implemented in VS2010 - C++ parallelism libraries, concurrent SQL CE intellisense databases and all. Keep up the good work.

Page 1 of 1 (3 items)