For me, programming is an intimately personal, creative activity - akin to painting or poetry. What you produce is a distillation of your thought processes on how to solve a particular task. Having someone observe and critique how your mind works - as it is working - is about the best way to destroy your flow or train of thought.
Totally agree with your point of view! :)
But keep in mind that splitting roles to the Driver and Navigator doesn't restrict your intimate thought process. Moreover, it encourages you to maximize your focus on the task. Navigator is the brains of the whole operation at the time. He constantly thinks about the whole process and should not be distracted by typing the code or the Driver's objections.
One of the mandatory rules of pair programming says: "trust the Navigator" :)
Wrong. It completely changes and restricts your thought processes as you keep having to articulate those thoughts in a way the driver understands (which may not be easy)... and give directions to the driver, hoping they'll follow them correctly
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I personally cannot think of a worse way of programming
Why do you think so? Have you tried it yet? :)
For me, programming is an intimately personal, creative activity - akin to painting or poetry. What you produce is a distillation of your thought processes on how to solve a particular task. Having someone observe and critique how your mind works - as it is working - is about the best way to destroy your flow or train of thought.
And yes, I have tried it... Never again
Totally agree with your point of view! :)
But keep in mind that splitting roles to the Driver and Navigator doesn't restrict your intimate thought process. Moreover, it encourages you to maximize your focus on the task. Navigator is the brains of the whole operation at the time. He constantly thinks about the whole process and should not be distracted by typing the code or the Driver's objections.
One of the mandatory rules of pair programming says: "trust the Navigator" :)
Wrong. It completely changes and restricts your thought processes as you keep having to articulate those thoughts in a way the driver understands (which may not be easy)... and give directions to the driver, hoping they'll follow them correctly