We're all remote: how we deal with a 100% remote dev team

Re:We're all remote: how we deal with a 100% remote dev team by garagebander on Monday March 28, 2011 @02:32PM (#2379448)

I don't think most business owners or bosses are mature enough for this yet... they just assume the remote worker is sloughing off.

No use trying to convince them otherwise... they think their staff is slackers. Period. (Not all business owners or bosses, just those that lack the maturity to direct a remote workforce.)

But for the seasoned manager, it's no problem at all.

[ Parent | on HN ]

Re:We're all remote: how we deal with a 100% remote dev team by japherwocky on Monday March 28, 2011 @02:47PM (#2379510)

This drives me nuts; either I'm checking (timestamped no less!) code into the repo, and delivering what I say I'll deliver by the appointed deadlines, or I'm not.

It's not like you can fake productivity as a coder.

[ Parent | on HN ]

Re:We're all remote: how we deal with a 100% remote dev team by technomancy on Monday March 28, 2011 @04:36PM (#2379970)

Let's be honest, coding is really only half the story. There's lots of deployment, debugging, and maintenance work that is much fuzzier and harder to measure. In fact, if you are actually actively coding for more than half your time, you're either really lucky or you don't have any users yet.

[ Parent | on HN ]

Re:We're all remote: how we deal with a 100% remote dev team by waqf on Monday March 28, 2011 @03:08PM (#2379607)

You can (or at least they'll assume you can) if you have input into your own deadlines: they'll say you're padding your estimates.

[ Parent | on HN ]

Re:We're all remote: how we deal with a 100% remote dev team by getsat on Monday March 28, 2011 @05:11PM (#2380115)

I love when non-coders tell me how long a coding task should take. This is one reason why I decided to work for myself.

[ Parent | on HN ]