| Newsgroups |
gmane.comp.programming.extreme-programming |
| Message-ID |
<CALaPUVeW0P5vQf70QnGdZWvCLfir_bxb8aM5qof+=w3Sj-eBxw@mail.gmail.com> |
On Fri, Oct 14, 2016 at 12:38 PM, Jeff Langr [email protected]
[extremeprogramming] <[email protected]> wrote:
>
>
> Hi Adam,
>
> I love the point about learning to pair live first.
>
> The isolation thing is not trivial--after longer periods of working
> remotely, you can start to lose important social connection and develop
> somewhat antisocial habits, attitudes, and feelings. In my case, I think I
> was started to get depressed, even with the pairing.
>
> On the flip side: We paired a bit too much at Outpace (where I was
> remote), on average 7 hours per day. It was effective, but I wasn't getting
> opportunities to explore on my own, which for me is important. By day end,
> I was so beat that I had zero interest in wanting to touch a computer after
> work. I barely blogged or tweeted for about two years as a result.
>
>
Interesting. I have burned out similarly from travel, but never from
pairing.
> (We were slamming through a lot of new, different technologies, too, which
> contributed greatly to my brain fatigue.)
>
> This isn't the first time, either; three different long-term experiences
> with all-day (7+ hour, 8-10 hours in one place) pairing convinced me that
> 6--remote or live--should be plenty for most mortals.
>
>
Yeah, I actually think 3-4 hours a day, in =< 90 min increments, is about
ideal, combined with another 3-4 hours of individual learning and less than
an hour of responding to emails. That’s what I strive for personally, and I
encourage others to experiment and find what works for them.