News for hackers. Stuff that matters.
Re:Fog Creek’s Remote Work Policy by utnick on Thursday September 12, 2013 @11:03PM (#6378323)
This seems like a lot of rules... and kind of unfriendly. Especially for just a short stint working remotely.

Whats the worst that could happen if one of the workers has a less than ideal setup while temporarily working remotely for a few days? Would it really affect company outcomes? If not, I think developer happiness would be improved by having a more laissez-faire attitude from management.

Re:Fog Creek’s Remote Work Policy by misterjangles on Friday September 13, 2013 @01:19AM (#6378809)
If you ever own a company and you find yourself writing a salary check to somebody who you suspect did jack-shit all week - it's kinda amazing how difficult it is to not go into Ebeneezer Scrooge mode. Even if you know that people are not "on" 24/7. It can be tough to walk by somebody's desk and see them screwing around on Facebook instead of working - when you are the guy writing the checks. It takes a lot of faith. This is the same whether they are working on site or remote. It's easy to talk a big talk about what a generous boss you would be - but it is very different when you are responsible for meeting payroll week after week. I would challenge anybody to try it.

Joel's rules strike me as a little more specific than necessary, but I can very much relate to his feelings. I have experienced devs "working from home" who disappear all day and hold up the whole team because we can't find them to ask a quick question. The point is that when you say you are on the clock - then you should be working. I personally wouldn't care so much about the exact specifics of your internet connection or whatever. But, if you tell me that you're working then I expect that you're actually at your computer working and not laying by the pool or playing video games.

It's equally easy to say that you'd just fire somebody who you did not trust to work at home with no rules. But, as with many things, it's easy to take this hard line approach with your imaginary company and theoretical employees - quite another thing in reality though. Some people are very productive but maybe not so disciplined. A few sensible rules and expectations can prevent problems.

Re:Fog Creek’s Remote Work Policy by redidas on Friday September 13, 2013 @10:40AM (#6380759)
Somebody not actually working at work could be due to many different factors. Yes one could be that they are lazy and half-assing their job, but it also could be that they just aren't motivated. Maybe they don't feel connected with their job. Ideally, an employee is motivated to to a good job for reasons other than its a daily grind and its what they have to do.

The HR industry terms this "Employee Engagement." If I had to guess, Fog Creek has quite a few "disengaged" employees.

Re:Fog Creek’s Remote Work Policy by misterjangles on Friday September 13, 2013 @12:37PM (#6381530)
Absolutely a great manager will inspire and motivate the team,. But, it is called "work" for a reason. Its a two way street. The employee has to put forth some effort as well. Your manager is not there to entertain you. At the end of the day you are there to work.
Re:Fog Creek’s Remote Work Policy by fphhotchips on Thursday September 12, 2013 @11:13PM (#6378359)
To me this isn't about seeming friendly or unfriendly, it's about defining boundaries of what is vacation time and what isn't. It's about saying "No, what you're doing isn't working from home, it's vacation. Don't feel guilty about not getting anything done, just go and have a break." Compare that to being fuzzy about it - you're not really having a decent break (because you're trying to get work done) and you're not getting any work done (because your 8 year old niece is pulling on your shirt, your brother wants to go golfing and your dad has the TV up extra loud).
Re:Fog Creek’s Remote Work Policy by LordHumungous on Thursday September 12, 2013 @11:47PM (#6378462)
That's why a good manager should define goals of things that need to get done. As long as the goals are being met, management should allow their developers the freedom to choose their own work environment and hours, within reasonable bounds. Demanding that your employees have headsets at home is called micromanaging.
Re:Fog Creek’s Remote Work Policy by kamaal on Friday September 13, 2013 @01:01AM (#6378757)
>>That's why a good manager should define goals of things that need to get done.

Good managers are nearly extinct species, whom you encounter once in a while in years. The remainder get to become managers by their political work and a results oriented work environment is something they will never build. Because if we were to measure progress by results, those managers will be the first to be fired.

>>As long as the goals are being met, management should allow their developers the freedom to choose their own work environment and hours

Their goals are very different than our goals. The goal of leaders is to produce results. The goal of management is to keep the wheels running, regardless of whether the running produces any results.

A good manager is automatically a leader.

Re:Fog Creek’s Remote Work Policy by fphhotchips on Friday September 13, 2013 @03:14AM (#6379117)
But it's not! If you're trying to maintain the communication benefits offered by an office structure, while also allowing WFH, his reasoning is actually pretty good. Laptop speakers are annoying, and hearing every key stroke from your laptop's keys is even worse. A headset is not even $20 - and a directional clip-on mic is even less.

Further, their goal is to encourage good work/life separation even when working from home. If you can't maintain that separation, it seems FogCreek would rather you clock it up to 'life' time than blur the lines. That's just good management - working with distraction is going to result in poor output. Goal oriented management in this scenario, particularly when this may not be a normal part of the workers routine, could result in stress and poor work. Far better that if you can't have a good work environment then you just take a break and increase your output when you get back.

Re:Fog Creek’s Remote Work Policy by seiji on Thursday September 12, 2013 @11:31PM (#6378413)
Yeah, it's an insane number of rules. (is video chat required? why video chat?)

Down the page they mention The burden is on you to show that you’re being productive. -- that just sounds outright authoritarian and demeaning. Strict policies calling people out as "do this ... or else" don't exactly engender trust.

I think they cover most of our complaints in the poorly worded Known availability and overlap with your team section.

Most places have three levels of "work from home." There's full speed "work from home" where you're getting more done because you're not distracted by office shenanigans. There's half speed "work from home" where you're not plowing through, but you're keeping up with all communications/chats and fully available if anybody needs you. Then there's fill-in-the-gap "work from home" where you're checking into work systems in the morning, getting some things done, going to an intermediate step in the middle [an appointment at the house, going to a doctor on the way to work at 11am, going to the DMV at 10:30am], then going into the office for the rest of the day.

I think they're saying all of the above is okay, just communicate what your availability will be up front (which seems to go against their other policies of "work in a nuclear fallout shelter away from all distractions and you better have no other responsibilities at the same time either — we own you").

Re:Fog Creek’s Remote Work Policy by jacques_chester on Thursday September 12, 2013 @11:49PM (#6378472)
> Yeah, it's an insane number of rules.

I think this is hyperbole. They all basically boil down to: if you work from home, please work from home. And keep in touch.

I work from home. As a rule, the best-running projects are those with daily video meetings. The 2nd best involve phone calls. The worst involve emails.

Faces have enormous bandwidth. Voices a bit less. Email has bugger all for the things that matter.

Re:Fog Creek’s Remote Work Policy by Iftheshoefits on Friday September 13, 2013 @12:16AM (#6378573)
As a rule...for you and your team. Companies like this don't pay developers for face-time, BS meetings just to "check in" (which is the vast majority of all face-to-face meetings), and so on. They pay us for our expertise in writing software or doing other similar technical work.

If a company offered me the choice between working from home under the conditions listed for Fog Creek or not working from home at all, I'd choose the latter and consider option c) quitting to obtain employment with a company that recognizes I'm not in kindergarten anymore, and don't care to be treated like I am.

Re:Fog Creek’s Remote Work Policy by jacques_chester on Friday September 13, 2013 @12:26AM (#6378619)
> Companies like this don't pay developers for face-time, BS meetings just to "check in" (which is the vast majority of all face-to-face meetings), and so on. They pay us for our expertise in writing software or doing other similar technical work.

They pay us to make business problems go away. It just so happens that our tool for that is usually software.

A major insight of agile methods is to put the developers close to the coalface, because infrequent or indirect contact leads to the wrong thing being built.

I frequently find while working with customers that we have entirely different mental models of the project. And I only find that out because I am constantly asking them questions about their business.

Re:Fog Creek’s Remote Work Policy by corresation on Friday September 13, 2013 @12:27AM (#6378624)
if you work from home, please work from home.

Do they have a "if you work in the office, please work in the office" list of rules?

My experience has been that most people "working" in an office aren't working at all for the overwhelming majority of their day. But that's just office life and it's just the way it is. Marissa Mayer wants everyone in the office because she wants to set a "good" example: businesses like Yahoo absolutely depend upon vacuuming away the activities of people sitting in droll offices.

Re:Fog Creek’s Remote Work Policy by tghw on Friday September 13, 2013 @02:02AM (#6378915)
An explicit one? No. But it's not needed, because there's a social pressure to be working. People can see you not working in the office. But if you're at home, no one knows if you're not working. So some guidelines are put in place.
Re:Fog Creek’s Remote Work Policy by seiji on Friday September 13, 2013 @12:06AM (#6378538)
Working from home also means: less stress because you don't have to be constantly "on" and playing the visibly social game eight hours a day (or pretending certain morons in the office aren't morons), slightly less availability (or non-interruptable availability on your schedule, not theirs) to get more focused work done, and no pants.

Perhaps "insane number" is wrong. I probably meant "insanely specific requirements."

The 1 wasn't even running to rector st this evening, so I couldn't get to work even if I wanted to.

Re:Fog Creek’s Remote Work Policy by breitling on Thursday September 12, 2013 @11:14PM (#6378362)
I get the same unfriendly feel from this piece, but I guess this is a company in transition from not allowing remote work at all to allowing it now. Hopefully, as it becomes more common, they will relax the rules a bit.
Re:Fog Creek’s Remote Work Policy by mistermann on Friday September 13, 2013 @01:49AM (#6378873)
Indeed, this piece was obviously written by a bunch of greenhorns.

For their sake I hope they take some of the sage advice offered in this thread from the numerous people who have run profitable businesses with multiple employees for several years.

Re:Fog Creek’s Remote Work Policy by tghw on Friday September 13, 2013 @02:05AM (#6378928)
How is this a lot of rules? As far as I can see, it boils down to three:

1. Be able to communicate with your team.

2. Have a place where you can work, distraction free.

3. Get approval from your team lead. (This one barely counts, since the answer would never be no.)

Re:Fog Creek’s Remote Work Policy by eropple on Saturday September 14, 2013 @01:41AM (#6384785)
> 2. Have a place where you can work, distraction free.

From working remotely for the last year, I've found that basically any table is a fine remote work spot for me. Kitchen table, Starbucks, whatever. I have learned that I don't get appreciably distracted by ambience or even really by light conversation[1] (unless doing something particularly out-of-the-ordinary in terms of difficulty, in which case it's lock-the-doors time); if I did have concentration issues, don't you--y'know--think that I wouldn't do the things that triggered them. Because I'm an adult and I'm competent? The assumption that people aren't is why, to me, these edicts read as kind of wacky.

[1] - Hell, I'm getting a coworking space because I find that that ambience and that light social friction makes me better at what I do. =)

Re:Fog Creek’s Remote Work Policy by jaggederest on Friday September 13, 2013 @04:02PM (#6382759)
#3 then becomes the worst kind of rule, one that is no only under unanticipated circumstances which are not going to be covered by rules, by definition.
Re:Fog Creek’s Remote Work Policy by wging on Thursday September 12, 2013 @11:19PM (#6378381)
Seems targeted at people who are remote long-term. Maybe a little more reasonable in that light. But for short-term people,

>Approval from your team lead. Basically, just tell someone well in advance if you’re going to be altering your work arrangement, temporarily or permanently.

seems counterproductive. Sometimes problems come up and you suddenly need to be at home tomorrow to meet the cable guy, who has committed to come between 6 AM and 9 PM, but will only be there for 15 minutes.

Re:Fog Creek’s Remote Work Policy by kevin on Friday September 13, 2013 @12:04AM (#6378527)
I think "approval" is less formal than you might imagine for a company like Fog Creek and most startups. Sending a quick email to let the person in charge know that you're going to be some place unexpected is totally reasonable.
Re:Fog Creek’s Remote Work Policy by slantyyz on Friday September 13, 2013 @01:19AM (#6378807)
Your point is right on, but I think Fog Creek has been around long enough to no longer be considered a startup.
Re:Fog Creek’s Remote Work Policy by wging on Friday September 13, 2013 @03:14AM (#6379118)
Then why call it approval?
Re:Fog Creek’s Remote Work Policy by pjzedalis on Friday September 13, 2013 @01:59AM (#6378907)
Well the real reason is FogBugz doesn't know how to predict productivity for remote workers.