Live data from Hacker News

Fog Creek’s Remote Work Policy

blog.fogcreek.com

71–80 of 128 posts

Re: Fog Creek’s Remote Work Policy

#71
post #3

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.

[deleted]

Re: Fog Creek’s Remote Work Policy

#72
post #9

This reads like yet another autocratic, micro-managing HR document. "Have a room with a door that shuts." Seriously? How about this: hire smart people you trust, give them whatever tools and support they need to do their jobs most productively, then get out of the way.

Well said!

Re: Fog Creek’s Remote Work Policy

#73

Earlier quoted context omitted.

From reading the comments in this thread, I don't think very many people in this thread know who Joel Spolsky is.

Or the alternate explanation, most of the people in this thread disagree with Joel Spolsky. Given occam's razor and his fairly high profile, which is more likely?

Disagreeing with Spolsky's writing is one thing, but unless you've seen or heard a lot of Fog Creek employees calling it a horrible place to work, then I would say that any speculation about how horrible a place Fog Creek must be because of the tone and content of the OP would suggest that Mistermann is right.

Re: Fog Creek’s Remote Work Policy

#74
Seems ridiculously anal to me. Our only policy is:

a) Make sure your team knows where you're at.

b) Get the job done.

No approval, know anal micromanagement about how you do your job. If you can deliver whilst sitting in the garden watching the kids, kudos to you.

Not coincidentally, the same policy applies to working in the office...

Re: Fog Creek’s Remote Work Policy

#75
post #61

Earlier quoted context omitted.

I'm just picking your comment at random out of this thread...do you know Joel Spolsky who runs Fog Creek? I'm reading all these critical comments in this thread and reconciling it in my head with what I know of him (from his extensive blogging and podcasting) and I'm thinking, have so many years passed that no one knows who this person is they're criticizing? For example: > I bet the managers or whatever they fancy t…

This blog post was not written by Joel, nor does not sound like Joel. I think the comments are justified; the blog post feels quite abrasive to me. It's a little hard to put my finger on it, but the repeated distinction between work and vacation is a bit grating. Contrast this with a company like Netflix that don't count vacation days, and that assume that it their job to ascertain the productivity of their employees…

>> Probably just unfortunate wording.

Yes. People sometimes spend too much time parsing tone of written text (hmm, I wonder why the OP talks about using video for face-to-face communication?).

I can't tell you how many times I've told people working for me to stop spending time parsing the tone of an email from a coworker or client and just pick up the phone and call them. Most of the time, any concerns with a poorly worded (or angry-sounding) e-mail are cleared up with a 2 minute conversation.

Re: Fog Creek’s Remote Work Policy

#76

Earlier quoted context omitted.

Well, if I was working at a low morale Taco Bell, then yeah, I think I would want to work at your local McD's. Otherwise, asking someone who works in technology if they want to work in fast food is kinda pointless.

> Well, if I was working at a low morale Taco Bell, then yeah, I think I would want to work at your local McD's. Yes, if you work in the industry equivalent of a low morale Taco Bell (dunno, Oracle?), Fog Creek sounds like a great place to work.

Oh the self confidence of the young. You'll cringe some day.

Re: Fog Creek’s Remote Work Policy

#77

"You still have stuff like chat, commit messages, code reviews, cases, Trello boards, etc. Be a little paranoid for this time about showing your work. It will help you feel good about your time, and us feel good about granting it." Run through a de-weaselizer, this reads: "Be a good little pet, and do an extra set of tricks when we take you out to the park, so you feel good about running around in the park and we fee…

As teams and companies grow larger they typically get dumber and become more focused on increasingly more trivial issues. It's the classic "streetlight effect". It's always easier to prioritize things that are easier to measure or more highly visible even when those things are fundamentally less important.

Re: Fog Creek’s Remote Work Policy

#78

Earlier quoted context omitted.

> Does that mean you would instantly want to work there? I really don't understand the point you're trying to make. Personally, I don't prefer micromanagement, but it doesn't make me unhappy if other things are being run productively.

> Personally, I don't prefer micromanagement, but it doesn't make me unhappy if other things are being run productively. What is this I don't even. So you don't prefer to be micro-managed, but you're fine if other people are? It doesn't work that way. This is a pervasive company culture. Either your company has these rules and everyone is micromanaged, or no-one is.

Hows about you stop and consider that you don't know everything, go back and read what was said in the thread, and think it over again.

At the very least, you have poor reading comprehension. You are not trying to understand what I'm saying, you are deliberately taking the worst interpretation of what I've written, to the degree that you're literally attributing to me things that I didn't even say.

Humility, civility, understanding, thoughtfulness, etc are very valuable and somewhat rare traits in the technology industry.

Re: Fog Creek’s Remote Work Policy

#79
post #3

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.

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.…

[deleted]

Re: Fog Creek’s Remote Work Policy

#80
post #3

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.

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.

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.

Post reply on HN