Not at all. I think that some folks just don't work well in such circumstances. A close friend of mine was much like you: he craved the social environment, and the immediate collaboration with peers. Personally, I'm the opposite. I hate drive-bys, I crave the flexibility to work when I want and how I want, and the social interactions offer no real value to me.
I think it's great that you know how you best work. It's a key to happiness.
> If developers are remote, you will find that your code-base becomes the same. That critical FooBarAdapter becomes something that only Naimh can work on because without co-location if another developer is stuck on it, rather than grabbing her for a "Can you look at this?" over the shoulder, it gets slung over the fence in an issue or pull request.
That's just patently false. Not only can this happen in co-located work environments, but is often symptomatic of a poorly functioning team rather than how they're located on the planet.
Not at all. I think that some folks just don't work well in such circumstances. A close friend of mine was much like you: he craved the social environment, and the immediate collaboration with peers. Personally, I'm the opposite. I hate drive-bys, I crave the flexibility to work when I want and how I want, and the social interactions offer no real value to me.
I think it's great that you know how you best work. It's a key to happiness.
> If developers are remote, you will find that your code-base becomes the same. That critical FooBarAdapter becomes something that only Naimh can work on because without co-location if another developer is stuck on it, rather than grabbing her for a "Can you look at this?" over the shoulder, it gets slung over the fence in an issue or pull request.
That's just patently false. Not only can this happen in co-located work environments, but is often symptomatic of a poorly functioning team rather than how they're located on the planet.