Attention: We are retiring the ASP.NET Community Blogs. Learn more >

Is structure good?

I've asked many programmers/developers about where they want to end up and, often the reply is: "Me?  I'm going to work for Microsoft.  Gunna cut some elite code working on the kernel!".  Which I always interpret to mean: "Me?  Well apparently Bill's got a shitload of money and he's giving everyone free Jolt cola... that's where I'm heading!".

Conversely, I've often been told by my peers that I should go and work for Microsoft.  Now, if you are reading this, and, like me, you are "relatively" sane you will roll your eyes and realize that this is an absurd notion.

Don't get me wrong, I will work for Microsoft one day, I'm reasonably sure of that, but I'm firmly of the opinion that you don't just walk through the door into Microsoft, you kick it down and you march in!  Basically, you get in because you deserve to be there and because you have something special to offer.

Anyway, so far, when asked "when" I plan to work for MS I've offhandedly replied "When I'm about 45".  Which leaves me with a rather interesting dilemma, I've got 10 years to earn the right to kick the door down.  What am I going to do?  How will I do it?  Will I need proof that I did it or will they just ask me those silly little puzzles?

Which all brings me to my current point of interest... you have the possibility to work for one of two companies:

Company A:
Mid-size, sharp, fast and focussed.  Chance to build dozens of small applications each year and work with the bleeding edge.  You can be raw, relatively free and creative.

Company B:
A software behemoth.  Lot's of process.  Chance to work on monolithic applications priced in the multi-million price range, surrounded by experienced and talented individuals with many years of experience.

Both doors are open.  Both doors may lead to Microsoft but, both take different paths.  Which door is most likely to succeed?

Over the next couple of days I'd like to solicit feedback about the relative pros and cons of working for big versus small-to-mid sized companies.  I've already received many opinions and I'll be compiling them into a future blog entry too.

7 Comments

  • I'm not aware of anyone that got an interesting job at Microsoft at age 45 without having one or two of these multi monster projects shipped or being some kind of celebrity. At that age you are either and architect or a manager which means you have responsibility for getting one of these monsters out. This in turn means you should have lots of experience in doing monster projects. Makes sense?

  • I should probably point out that, in my example, Microsoft can be substituted for *any* company.



    The company itself is academic, feel free i\to replace it with whatever you expect to be doing when you are 45. The arugument is really to weigh up the pros and cons of different types of organisations.

  • This is something I've actually been considering a good bit lately. I fit my current employer into the small to mid-size range. The one problem I've had here is that I get to work on a lot of small to medium sized applications but they are all very similar. They don't pose any substantial challenges that really cause my brain to hurt. I've found that problems that make your "brain hurt" are the ones that really challenge you professionally to learn new things and take yourself to the next level. So, in summary I guess my opinion is that it doesn't matter if its big or small its the "brain hurt factor" that makes the most difference.



  • If you think you're good enough to work for Microsoft, then you probably have a strong sense of self-motivation, creativity, passion, and entrepreneurialism.



    If that's the case, why not work for yourself and do something truly original?



    Granted, working for Microsoft you'll have access to incredible resources and work with some of the most talented people in the world but, at the end of the day, you're still working for the "man".



    Why not work for yourself instead and build your own empire?



  • Tried 2200 people. Tried 30.



    30 is the definite answer when it comes to fast moves, fast software development, simpler requirements, and best of all, less meetings and less processes.



    Can't even see the point now of working in big fat companies, except if I wanted to make a career and have planned that I would stay there ten years or so.

    This never happened to me so far. The innovation is in small companies. The personal interest and motivation is with them too.



    I wouldn't stay long in a company that tells me to do many things without the freedom of doing them. Microsoft has admitted a lot of corporate greed so far. There are also books about it.

  • I'm sure there is an explanaition for this but it might be a long and complicated one. Think about it, why would a team at Microsoft hire a 40 year old guy without any special qualifications when the same team can get a motivated 25 year old Stanford graduate? The first question I would ask in such a case is: "Why are you hiring me and not that 25 year old kid?". Usually you find the exlanation a year into the job.



  • LMAO! You must be the 40 year old programmer (who has the wisdom of experience to come up with an answer like that!)

Comments have been disabled for this content.