>>>This is one of schemes where it's not "location, location, location", it's "communication, communication and source control".
>
>
>>Yes but most of IT managers do not know how to control telecomuting developers. They even do not know how properly to cut into pieces the project.
>
>Then they need to either get a different IT manager or hire a Project Manager. There is no reason these days for someone to get on a plane and travel 1000's of miles to do something that can be done over the internet.
I've been working with one such person. He'd design and redesign several times, and say "do it" only to change his mind after seeing how his ideas worked when they hit the screen. Above all, he'd require my presence on an occasional Saturday - which was a complete waste of time, because he didn't have anything for me to do; I'd usually sit out while he was in a meeting. And, of course, we hade an outsourced team, which was sitting idle most of the time.
Somehow, I think the guys who have a problem handling telecommuters have the same problem with all of their flock being in the same pen.
>>Most of them prefer peopple to be on-site and they to be able to get full controll on their actions.
>
>In most cases (at least right now) this is probably true, but again - then perhaps they need to hire better programmers that they know can do the job without constant supervision and guidence. I think over the next few years you will see more people and companies taking this view point.
As my father uses to say, "from your mouth into God's ears".
Really, what's the problem some managers have with telecommuters? Cut the stuff into deliverables, track delivery, whoever's too late or doing wrong stuff, g'bye. And if the really good guys do their stuff in five hours a day instead of eight - so what? They could have done the same thing in the office, and lose three hours each day on meetings, walking to the restroom, going out for a smoke, chatting around the coffee machine... anything. Plus they'd waste their own time driving to work.
