egg timers

Max Guernsey, III wrote:

Have you considered making it a goal for yourself to switch before the alarm
goes off? You run the risk of using this tool as a crutch and not delving
into the root of the problem.

Point!

Finally, you might try to "blow your pair away" while they are the ones
typing; it's far more gratifying for me.

That topic is "LetJuniorMakeMistakes". The navigator should always prefer a Goal
Stack, on paper, over interrupting Junior. Even if that means goals like "fix
the ugly construct they wrote in the other file that could have been one line".
Develop a secret code for that one.

Cenk wrote:

This practice make sure one developer does not own the keyboard for
more than 10 mins.

I could point out this technique is good for LetTheJuniorDrive - if I weren't
personally capable of >ahem< blowing most programmers away

Victor wrote:

>Do you mind telling us how did the timer experiment work for you? After a
>while. Let's say 2 months, to let the effect of novelty fade away.

Sure! But the juniors will be more resilient by then.

Another good technique, as posted, is one side writes the test or code, and the
other side writes the code or test.

(Now alla y'all go back to your holiday weekend already!)

--
Phlip