News for hackers. Stuff that matters.
Re:Working at Microsoft – Day to Day Coding by dikbrouwer on Monday February 28, 2011 @12:22AM (#2270151)
I'm a bit confused by this post. The author seems to celebrate a private office. I strongly prefer open work spaces that you share with others, as do many companies I've worked with/seen. Care to share your opinion? I'm curious...
Re:Working at Microsoft – Day to Day Coding by Locke1689 on Monday February 28, 2011 @12:47AM (#2270209)
I shared an office in one situation, worked in an open space in another, and had a private office in a third. Private office was by far the best situation. Being able to grab complete silence when necessary was amazing. Private offices end up being the best about 90% of the time. When you do need to collaborate, conference rooms are available and using laptops isn't hard. Most offices can also support about 2-3 other co-developers with ease.

If I had a choice I would choose a private office every time.

Re:Working at Microsoft – Day to Day Coding by rdouble on Monday February 28, 2011 @02:47AM (#2270489)
I've worked at startups with open plans for the past 12 years. At every one, it starts out ok when there are less than 10 people. As soon as there's about 20, almost all of the important programming work is done after hours when all the loud people are no longer there. The only thing that gets done during the day (programming wise) is putting out fires. I've come to the conclusion that half the reason startups require "insane hours" is because during the day, the programmers are distracted and only working at 20% capacity.
Re:Working at Microsoft – Day to Day Coding by maximilianburke on Monday February 28, 2011 @02:27AM (#2270455)
I've done both and much prefer offices. It's much easier to collaborate in an office than it is to drown out distracting noise from a shared workspace. Offices don't keep you from being able to swing by someone's desk or have someone drop by yours, unless you shut your door for a reason.

My current area at work is open and I have to on occasion bring ear plugs to keep the noise down to a level where I can concentrate. There are group meetings, conference calls on speakerphone, and loud personal conversations happening all the time. IMO, if it comes to needing ear plugs then the one purported benefit of working in an open area is lost since you can't really be sharing/collaborative if you've closed yourself off.

Re:Working at Microsoft – Day to Day Coding by plinkplonk on Monday February 28, 2011 @12:49AM (#2270216)
"The author seems to celebrate a private office. Care to share your opinion? I'm curious..."

From experience, my most preferred to least preferred office options are

(1) Work from home (2) private soundproof office with a door (3) shared sound proof office (2 or 3 people in a medium/large room) with a door(4) open work spaces with a maximum of 5-8 people (5) standard cube (6) crowded and noisy "open work spaces" where you can't hear yourself think / get interrupted all the time, especially the "agile" version with enforced pairing and the "buzz of conversation" and so on.

The best options give you silence. The least inundate you in noise.

Re:Working at Microsoft – Day to Day Coding by absconditus on Monday February 28, 2011 @01:18AM (#2270307)
In my experience open spaces are preferred by those who are less competent and want to bother me all day with questions.
Re:Working at Microsoft – Day to Day Coding by nostrademons on Monday February 28, 2011 @01:20AM (#2270313)
You never ask people questions when coding?
Re:Working at Microsoft – Day to Day Coding by prodigal_erik on Monday February 28, 2011 @02:19AM (#2270443)
My favorite argument comes from http://www.joelonsoftware.com/articles/fog0000000068.html : "Mutt can't remember the name of the Unicode version of the strcpy function. He could look it up, which takes 30 seconds, or he could ask Jeff, which takes 15 seconds. Since he's sitting right next to Jeff, he asks Jeff. Jeff gets distracted and loses 15 minutes of productivity (to save Mutt 15 seconds)."

If a question isn't an emergency, I queue it up by sending email. If it is, I ask in person, fully realizing I'm fucking up their day and hoping that doing so really is in the best interest of the company. I also only check my email a couple of times per day and wear heavy closed headphones for coding, because those elusive moments of flow are about half of what I live for.

Re:Working at Microsoft – Day to Day Coding by danenania on Monday February 28, 2011 @05:26AM (#2270800)
"fucking up their day"

This is interesting--I would never feel this strongly about being interrupted unless someone was being overtly rude or annoying. I want to be productive, but I don't feel obligated to plow forward relentlessly hour after hour. If someone breaks my flow to ask a reasonable question, I don't think of it as a big deal. I think true flow is a lot less fragile than many give it credit for. It doesn't vanish anytime a pin drops nearby.

I think there's something to be said for the benefits of a less serious and more relaxed mindset. Working steadily, but not getting all caught up in "how productive am I?" like you're an assembly line robot. Coding is as much an art as a job and often you can be more productive by playing ping pong and chatting for 6 hours then having an insight that saves you 100 hours in the long run because your mind makes a lateral leap about the architecture that almost definitely wouldn't have happened if you had just sat at your desk typing all day.

I still see the benefits of private offices because it can be very beneficial to have the option of silence and intense focus when that is what you need to get over a hump, but it also seems like a lot of programmers are missing the great potential rewards of real creative collaboration--probably because they are used to collaborating in an uptight business-guy kind of way. Instead, they should take a cue from other creative people like artists, poets, and musicians, and allow their minds be free a good portion time through relaxation, speaking freely, and gasp having plenty of thoroughly unproductive fun. The gains in inspiration will easily outweigh the lack of perspiration, and life will become more enjoyable to boot. Isn't that ultimately the point of all this toil anyway?

Re:Working at Microsoft – Day to Day Coding by nostrademons on Monday February 28, 2011 @05:43AM (#2270824)
I'll admit to sometimes getting annoyed when I'm interrupted and lose my train of thought. I like to code, damnit, it's hard when something keeps me from coding. :-/

But I've also found that my stress level just dropped so much when I acknowledged that I get nothing done during business hours, and so ought to just go in and accept the fact that my job is to help other people get things done. I can still fit in 2-3 hours after dinner, once everyone's gone home, and I found when I was doing my startup that 3 hours is about the maximum time per sitting that one can spend doing high-level intellectually creative work without getting totally burnt out. The unfortunate part is that it time-shifts my day (I go in to work around 1:00 PM and work till 9 or 10 at night), which means I only see the sun for half the day. But with enough practice (obviously failing now, since it's almost 3:00 AM), maybe I could swing my sleep schedule around and just have the mornings off to do whatever I want, then go to sleep as soon as I get home from work.

Re:Working at Microsoft – Day to Day Coding by prodigal_erik on Tuesday March 01, 2011 @04:31AM (#2274828)
I don't mean to sound like I'm chaining myself to the oars, and it's all a matter of degree. Talking design or shooting the breeze with the other guys is great and all, but sometimes I already know what I need to build if only everyone would just let me keep it in my head long enough to get anywhere on it. I find Joel's "15 minutes" optimistic. When a dozen people need immediate answers about stuff I haven't thought about since last year, and I try and fail a dozen times to actually write some code only to go home exhausted without a single commit to my name, it's utterly demoralizing. I go out of my way to respect others' time in the zone as an overreaction to how rarely mine is.
Re:Working at Microsoft – Day to Day Coding by arethuza on Monday February 28, 2011 @05:50AM (#2270841)
For me it really depends on what the question is - if I was in the middle of coding and someone asked me a coding related question (especially about whatever we were working on) then that really wouldn't require a context switch.

However, if someone non-technical comes and asks me something (which usually requires a lot of parsing) then that will require a context switch and I will loose a chunk of productivity.

Re:Working at Microsoft – Day to Day Coding by danenania on Monday February 28, 2011 @06:14AM (#2270888)
Some of it for me is pure selfishness. I just care a lot more overall about having an interesting day than being productive. An interesting day includes work and solving problems, but it also includes conversation on both technical and random human topics, connecting with people on a deeper than working level, and just plain screwing around. Luckily this all tends to balance out (at least), because maintaining high spirits and an active imagination gives a boost to productivity that's at least as strong as having a private office and slogging away in it stoically every day for 10 hours.
Re:Working at Microsoft – Day to Day Coding by absconditus on Monday February 28, 2011 @01:23AM (#2270327)
I am not opposed to all questions. I am opposed to the questions that are typically asked by those who prefer open spaces. I am also not opposed to basic questions asked by those who are new to the field, but I am often asked basic questions by those with 3+ years of experience.

Read a book.

Re:Working at Microsoft – Day to Day Coding by nostrademons on Monday February 28, 2011 @01:39AM (#2270366)
It's possible we just know different people who prefer open spaces, but the questions I'm frequently asked are more specific variations on "How does Google's serving and indexing pipeline work?" and "What are the best practices for building JavaScript-heavy webapps in an environment where latency matters?"

There are obviously no books about those topics (well, there are some about the latter, but they're all wrong, and we have experimental data to prove it). And even if they were, they'd be out of date before they were published. Google's indexing system changed completely when Caffeine was launched last year - the only way to get information about it is to ask the people who're responsible for developing it. And the ecosystem surrounding the web is continually changing, and we keep running new experiments to keep up with it, because things that we were absolutely certain were true 5 years ago no longer are.

Re:Working at Microsoft – Day to Day Coding by absconditus on Monday February 28, 2011 @01:55AM (#2270397)
Most companies are nothing like Google.
Re:Working at Microsoft – Day to Day Coding by astrange on Monday February 28, 2011 @10:42AM (#2271547)
> What are the best practices for building JavaScript-heavy webapps in an environment where latency matters?

Well, what are they?

Re:Working at Microsoft – Day to Day Coding by nostrademons on Monday February 28, 2011 @03:21PM (#2272729)
At the moment, confidential. Google derives a competitive advantage from being fast.

I've toyed with the idea of getting permission to release some of the results we've discovered, in maybe a blog series like what Crockford did for JavaScript at Yahoo. Google also derives a strategic advantage from the rest of the web being fast, and IMHO the benefits of making everyone else fast outweigh the benefits of being faster than everyone else. But I've already got a 20% project that takes up like 50% of my time, so I don't have time to organize something like that. Maybe later.

Re:Working at Microsoft – Day to Day Coding by theoj on Monday February 28, 2011 @12:41AM (#2270193)
The idea is that developers should have a quiet, distraction-free space to do their coding. With open spaces and cubicles you hear other people's conversations and you cannot reach the deep focused attention that you need to produce good, bug-free code.
Re:Working at Microsoft – Day to Day Coding by whakojacko on Monday February 28, 2011 @02:20AM (#2270444)
A decent semi-open setup has you not seeing much other than your monitor, and not hearing anything because you have good (company paid for) headphones on. And like others have said, If I can always WFH when I feel it is necessary.
Re:Working at Microsoft – Day to Day Coding by petercooper on Monday February 28, 2011 @01:10AM (#2270280)
Different strokes for different folks. And not only that, sometimes people vary in their preferences depending on the context. I like working alone at night most of the time but sometimes a busy coffee shop really does the trick.
Re:Working at Microsoft – Day to Day Coding by egor83 on Monday February 28, 2011 @02:12AM (#2270434)
A poll about preferred work environments: http://news.ycombinator.com/item?id=2270424
Re:Working at Microsoft – Day to Day Coding by SkyMarshal on Monday February 28, 2011 @02:27AM (#2270456)
It's all explained in the book Peopleware, along with years of data to back the conclusions.
Re:Working at Microsoft – Day to Day Coding by seanalltogether on Monday February 28, 2011 @12:54AM (#2270231)
I'm right there with you. The informal collaboration possible in an open space is so much more productive for me.
Re:Working at Microsoft – Day to Day Coding by InclinedPlane on Monday February 28, 2011 @02:29AM (#2270457)
Why do you imagine that informal collaboration isn't possible with offices? It happens all the time. Maybe you're just being prejudiced against a situation you have no experience with?
Re:Working at Microsoft – Day to Day Coding by seanalltogether on Monday February 28, 2011 @12:21PM (#2271929)
Because I've worked in both environments. I say informal because in open spaces you get involved in conversations and collaborative efforts that normally you have to go out of your way to be involved in. Here's a good example.

I was having a conversation with a dev about building an iPad app in my spare time and another dev sitting near by jumped in and argued that I should focus my efforts on the Mac App Store since it would be new and relatively easier to get noticed. 3 months later and I have an app selling well enough to quit my job if I really wanted to. This golden little side comment would not have happened if we all had offices.

Re:Working at Microsoft – Day to Day Coding by redthrowaway on Monday February 28, 2011 @01:05AM (#2270262)
Ideally, I'd like both: an open space to collaborate in, and a quiet place tucked away from interruptions and distractions to code in.
Re:Working at Microsoft – Day to Day Coding by andrewflnr on Monday February 28, 2011 @01:26PM (#2272211)
This. People get hung up on this type of debate when there's a perfectly obvious hybrid solution.
Re:Working at Microsoft – Day to Day Coding by duhmain on Monday February 28, 2011 @06:41AM (#2270931)
Open office spaces are great! For socializing, that is. If you actually want to get work done, peace and quiet is a must.