News for hackers. Stuff that matters.
Re:It Takes 6 Days to Change 1 Line of Code by DougBTX on Thursday May 17, 2012 @07:33PM (#3989665)
Tim Schafer, of http://www.kickstarter.com/projects/doublefine/double-fine-a... fame, has a note on his door until 11am in the morning saying, don't knock, writing. Could you make progress on projectY if you made a deal to not work on projectX until 11am? To not even open your office door?

(FWIW, this is a classic Quality of Service (QoS) algorithm, where traffic on ProjectY is given dedicated bandwidth (2 hours in the day) so that it isn't swamped by traffic from ProjectX.)

Re:It Takes 6 Days to Change 1 Line of Code by ojbyrne on Thursday May 17, 2012 @07:47PM (#3989710)
Door? Who has those anymore? In the interest of collaboration open-plan offices have become the norm, to the detriment of productivity everywhere.
Re:It Takes 6 Days to Change 1 Line of Code by badclient on Thursday May 17, 2012 @08:04PM (#3989745)
Funny enough I didn't get a private office but we got walls built for a private office when the sales guy joined because he was disturbing everyone. If my non developer coworkers realized how disturbing it is to be in flow writing code to have someone tap your shoulder and start discussing a totally unrelated issue to what you've been coding.
Re:It Takes 6 Days to Change 1 Line of Code by jrs235 on Thursday May 17, 2012 @08:33PM (#3989813)
My place of employment is similar to yours, I've moved myself up the ladder in order to start isolating and enabling my dev team the peace and quiet they need to be most productive.

What if, while you code, you think out loud, like really out loud... louder than you would talk in conversation? Perhaps if YOU bothered EVERYONE then maybe they'd put you in a private office? It's worth a try while you are looking for other opportunities...

i.e. "LET ME THINK HERE... IF VARIABLE V EQUALS ENUM ACTIVE THEN CALL DOHICKY ELSE DO NOTHING... WAIT IS THAT RIGHT?! NO NO NO LET ME RETHINK THIS?! I BET IF I REFACTOR THIS CODE I CAN..." All day long...if they tell you to be quiet tell them to "shut up" you're trying to think and they are ruining your thought processes and they risk causing you to slow down and/or enter errors and bugs into the code... "what do you mean me talking and noise in general is disturbing to you and your work? How they hell do you think I feel?!?!?" :)

Re:It Takes 6 Days to Change 1 Line of Code by mahyarm on Thursday May 17, 2012 @09:09PM (#3989923)
That kind of passive aggressiveness will make your coworkers hate you and could get you fired because they know you don't have to do that.
Re:It Takes 6 Days to Change 1 Line of Code by jrs235 on Friday May 18, 2012 @12:03AM (#3990309)
Apparently that passive aggressiveness already exists in his work place thanks to his bosses and co-workers... but some how you all fault him and say he can't share that same love?
Re:It Takes 6 Days to Change 1 Line of Code by mahyarm on Friday May 18, 2012 @03:24AM (#3990752)
I was thinking more about other situations. I thought the salesman was isolated to an office because he has to talk on the phone, constantly, to customers and it was interrupting the developers. I've heard similar situations with startups and their CEOs. If I did that in my open space office, my coworkers would just get irritated and eventually I'll be talked about it by my manager.
Re:It Takes 6 Days to Change 1 Line of Code by jrs235 on Friday May 18, 2012 @06:47AM (#3991187)
In fact, in my current work environment, when we moved offices there was a "central" open area with a view half built cube walls. Originally our telephone support were going to sit there and the Dev team was going to get placed in an enclosed shared Dev "war room". Support squeaked and the timid dev team got stuck out in the open.

Supposedly since Support is on the phone, they would interrupt everyone (everyone else int he vicinity is sales and they each have private offices) since they talk aloud on the phone. Why's this bad? Because breaking deep thought vs. some noise in the background (which still also exists because of the leakage they have on the phone in a single enclosed room) is much much more unproductive. Worse, the Sales team often forgets to shut their doors so sound leaks out into the open area or between sales calls they congregate a few at a time and have loud conversations disrupting the dev team. Worst of all is if they are in their offices, quietly doing paperwork with their doors open then decide to yell to talk to another salesperson in another office.

I often get up and shut Sales office doors, and constantly have to hush people up. My timid dev team doesn't because, well they are timid and don't want to rock the boat and add friction to inter office relationships. (I can hear, I agree. I need to encourage my dev team to speak up more, perhaps I'm sheltering them too much.)

Re:It Takes 6 Days to Change 1 Line of Code by jrs235 on Friday May 18, 2012 @06:38AM (#3991163)
unfortunately in environments like the one the OP mentions, the squeaky wheel is usually the one that gets the grease. So, while attached to the trailer (company) you're best to squeak loudly while you look for a better vehicle to get onboard with.
Re:It Takes 6 Days to Change 1 Line of Code by jrs235 on Thursday May 17, 2012 @10:18PM (#3990108)
But if you are planning to leave, what harm will it really do? When you have pocket aces, bet and play them!

EDIT: Maybe you'll inadvertently help the next guy. Yeah they might not care much for you but maybe, just maybe, something will click and the folks will realize... yeah I guess disturbing him was stupid on our part. If not and they don't get it... who gives a crap about people that don't give a crap about you!?

Re:It Takes 6 Days to Change 1 Line of Code by eli on Thursday May 17, 2012 @10:33PM (#3990141)
That's not playing a good hand, that's being a dick simply because you can probably get away with it. Don't be a dick.
Re:It Takes 6 Days to Change 1 Line of Code by aangjie on Friday May 18, 2012 @07:04AM (#3991227)
I sometimes am forced to do this at work. Just to get people to shut up from chit-chatting/small-talking very loudly. But then, I work in a cost-cutting, off-shored, cubicle farm.
Re:It Takes 6 Days to Change 1 Line of Code by Mc_Big_G on Thursday May 17, 2012 @09:36PM (#3990000)
Often, when we are pairing at work, the person driving is thinking out loud or the pair are in discussion with 8 other pairs in their row of tables.
Re:It Takes 6 Days to Change 1 Line of Code by megablast on Friday May 18, 2012 @05:22AM (#3991013)
If you only you could talk to them?

Seriously, most of these problems are due to lack of communication, set up a ticketing system, teach people how to use it.

Re:It Takes 6 Days to Change 1 Line of Code by sdfjkl on Thursday May 17, 2012 @08:21PM (#3989778)
Be a grumpy bastard. Someone taps me on the shoulder, I'm grumpy the first time, I growl the second time and if there is a third time I'll shout at them. Hasn't come to the shouting yet (although one guy got pretty close, but I just glared at him last time he approached and he grasped it).

Also, ask if you can work from home since your office environment is bullshit for writing code.

Re:It Takes 6 Days to Change 1 Line of Code by badclient on Thursday May 17, 2012 @08:51PM (#3989861)
Work from home was turned down pretty quickly though I'm not sure if that would have addressed the root problem. I think the root issue is they need a developer who just does tech support for the other 10 non tech people. And then a developer who can actually build shit quietly.

If my whole job was to do tech support all day there would be no problem. Of course it wouldn't be fun and I'd prolly end up leaving, the present situation hasn't been much better and I'm on my way out.

Now that I am leaving soon my boss is very interested for advice on how to attract tech talent. A part of me just wants to send him a link to this thread :)

Re:It Takes 6 Days to Change 1 Line of Code by jimbokun on Thursday May 17, 2012 @10:22PM (#3990117)
"A part of me just wants to send him a link to this thread :)"

That's probably the single best thing you could do for him, if he is serious about wanting to attract (and retain!) good technology people.

Re:It Takes 6 Days to Change 1 Line of Code by pilsetnieks on Friday May 18, 2012 @05:58AM (#3991088)
Re: working from home

Been there, done that. The only difference is that they call me on the phone instead of coming up to my desk.

Re:It Takes 6 Days to Change 1 Line of Code by nostrademons on Friday May 18, 2012 @03:31AM (#3990765)
I'll frequently work from home in the morning or evening if I want to get stuff done; no coworkers there. Or if I need to concentrate, I'll leave my office and go find a massage chair or cozy nook and curl up with my laptop, or even go to a different building and work alongside a team where nobody knows who I am.

Only thing I miss is my 3 24" monitors.

Re:It Takes 6 Days to Change 1 Line of Code by swah on Friday May 18, 2012 @10:57AM (#3992169)
So how well does Linux support that setup? Or you're using OSX at Google?
Re:It Takes 6 Days to Change 1 Line of Code by nostrademons on Friday May 18, 2012 @04:42PM (#3993836)
Linux supports 2 with no problem. I'm using a second computer and synergy for the 3rd.
Re:It Takes 6 Days to Change 1 Line of Code by lukeschlather on Thursday May 17, 2012 @09:38PM (#3990004)
I think there's a definite benefit to team offices, but the team needs to be focused on the same project.
Re:It Takes 6 Days to Change 1 Line of Code by prawn on Friday May 18, 2012 @04:21AM (#3990875)
Wear some sort of ridiculous Productivity Hat with a door on it somewhere and an 'Occupied' sign.
Re:It Takes 6 Days to Change 1 Line of Code by paddy_m on Thursday May 17, 2012 @07:50PM (#3989716)
the key part of that story is that Tim Schafer has a door.