Old fashioned is right, and disregarding
"telecommuters" is also extreemly short sighted and ultimaty limits your ability
to provide the most quality solution...
I work for Cisco Systems in our RTP (NC)
office. I work with two different groups, one based in San Jose and the
other based in Ontario, as a "virtual team member" (what we call our
telecommuter positions). I only bring all this up because I'm in exactly
the role you've outlined here, and to be honest I don't think I would BE as
successful as I am if I were located directly with either of these
teams.
The need to have everyone "all together" is usually
indicative of a larger problem in team dynamics, and communications. It
usually represents a team in which "charasmatic" leadership is more important
than technical know how or ability to get a job done. Now don't get me
wrong, for a person to BE a successful "virtual team member" they have to have
great communication skills, and be open to working with others in multiple
formats to enable the best level of teamwork and participation.
With all this said, and based on my own personal
experience in this role, I can tell you that what you're asking for here is a
person to walk a VERY shape edge between the need to bring the best and
brightest from people, without making it seem "personal". Actually having
this role as an "outsider" to the day to day politics and interpersonal sabatoge
of most bay area offices (yeah I lived there five years during the "boom") ,
gives a layer of abstraction that makes the job easier to perform. When
someone is questioning things like style, or code effeciency it comes
across MUCH easier (more acadimic) when that person is a "talking head", an
IM box, or a voice on the telephone. It becomes less "personalized"
and easier to "pick and choose" the best componants into a greater whole.
It also isolates the individual who may end up doing a lot of refactoring to
present the final solution.
Just something to consider. Open youself to
the best people in the world and don't accept just the best you can find in your
area, and you'll find that you solutions aren't also as limited...
-Zac Morris
|
- [JOB] Crack OOP Perl whitebox tester wanted Tom Mornini
- Re: [JOB] Crack OOP Perl whitebox tester wanted Phil Dobbin
- Re: [JOB] Crack OOP Perl whitebox tester wante... Dave Hodgkinson
- Re: [JOB] Crack OOP Perl whitebox tester wante... Stas Bekman
- Re: [JOB] Crack OOP Perl whitebox tester w... Phil Dobbin
- Knowing your limitation - was Re: [JOB] Crack OOP ... Zac Morris
- Knowing your limitation - was Re: [JOB] Crack ... Tom Mornini
- Re: Knowing your limitation - was Re: [JOB... Gunther Birznieks
- Re: Knowing your limitation - was Re: ... Zac Morris
- Re: [JOB] Crack OOP Perl whitebox tester wante... Ged Haywood
- Re: [JOB] Crack OOP Perl whitebox tester w... Per Einar Ellefsen
- Re: [JOB] Crack OOP Perl whitebox test... David Jacobs
- Re: [JOB] Crack OOP Perl whitebox... Vlad Safronov
- What is the right way of auth... Vlad Safronov
- RE: [JOB] Crack OOP Perl whitebox tester w... stevea
- OT Job discussion, was Re: [JOB] Crack OOP... Tom Mornini