News for hackers. Stuff that matters.

paulcam

Re:Working at Microsoft – Day to Day Coding on Monday February 28, 2011 @06:15AM (#2270890)
This is why code coverage numbers are a much better metric.
Re:Working at Microsoft – Day to Day Coding on Monday February 28, 2011 @06:12AM (#2270880)
Just a slight correction: the towels mentioned here aren't paper towels, but real actual towels. Many MSFT buildings have showers stocked with towels. At one point, the towel service was discontinued as a cost-saving measure. Lots of employees took issue with this and wanted their towels back.
Re:Working at Microsoft – Day to Day Coding on Monday February 28, 2011 @06:06AM (#2270871)
I'm just going to leave this here: http://www.pcmag.com/article2/0,2817,2361579,00.asp
Re:Working at Microsoft – Day to Day Coding on Monday February 28, 2011 @05:52AM (#2270844)
Team/building dependent. On my team, the vast majority of interns get a private office. When they get doubled, they get doubled into a window office.
Re:Working at Microsoft – Day to Day Coding on Monday February 28, 2011 @05:50AM (#2270840)
Entirely depends on team and building. I wasn't doubled up until my 3rd year at MSFT. Even then, it was due to cramped space (bldg 9).
Re:Working at Microsoft – Day to Day Coding on Monday February 28, 2011 @05:45AM (#2270831)
I think you might be misinterpreting the first post you linked. He's not bragging about how complicated it is. He's also not complaining about how tricky it is. There are always things in the Windows org that could use improvement (otherwise, I'd be out of a job). However, the vast majority of processes exist to fulfill requirements that very few software projects have to deal with.

Consider that Windows ships in over a hundred languages to hundreds of millions of people. I'm not sure how many languages Linux ships in (I'd bet quite a few), but Linux contributors don't have to worry about getting arrested for drawing map lines wrong: http://blogs.msdn.com/b/alexbarn/archive/2004/08/20/217602.a...

Do we ship software without testing? No. Do we ship software that isn't globalized? No. Do we just hack something together, check it in, and call it a day? No. These aren't the kinds of practices that lead to a stable platform.

Mistakes get made (at all levels of the management chain), but they tend to be the exception in my experience.

Re:Working at Microsoft – Day to Day Coding on Monday February 28, 2011 @05:30AM (#2270807)
> It's the really new, junior guys that don't get them right away.

I've been at MSFT for 9 years and have yet to be issued a laptop. I've been MSFT for 9 years and have yet to actually need a laptop. :)

Re:Working at Microsoft – Day to Day Coding on Monday February 28, 2011 @05:27AM (#2270802)
9 year softie here (Shell Test in my early days, now doing Dev work)

Indeed everything is dependent on need. PMs always get laptops because they spend lots of time outside of their office. On my team, most dev leads are also issued laptops. Friends of mine in teams closer to laptop features (think Windows 7 touch input, for example) never have had problems getting a laptop. On my current team, it's not common for an IC dev to have a laptop. It's also not common to find an IC dev with a machine more than 8 months old. I haven't quite figured out what everyone else's fascination is with laptops. I bought one for my own personal use, brought it to work, and then stopped bringing it because it just sat on my desk doing nothing 95% of the time. The other 5% I've replaced with post-it notes which, I'm happy to say, are available to both PM and Dev.