[Phpwm] Job for web programmer

[Phil Beynon]

> > David
> > How does the methodology of pair programming work when a person is on
> > "thinking time"?
> > In that when I am doing complex coding I will often wander off thinking
> > about what the correct methodology out of a selection of possibles might
> > actually be to tackle a problem as opposed to just sitting down
> and coding
> > the first thing that comes into my head and hoping it will work.
> >
> We don't actually ever just jump into code.  That's another reason for
> us to all work in the same place.  We spend time at the beginning of
> each project and when we come to new/potentially difficult things
> discussing how we're going to implement it.  We'll either discuss as a
> whole team (all 4 of us) or in smaller groups.  We make extensive use of
> our whiteboards to describe ideas, and come up with an approach before
> we sit down to work.  Then, once we're coding - especially when pair
> programming, we discuss issues as we're going along.  Pair programming
> is supposed to include a fairly constant dialog about what is happening
> - the navigator should be asking the driver why they're doing certain
> things or doing something a certain way, and making suggestions about
> how else they might do it while keeping in mind how the code fits into
> the larger scheme of things.
> The idea is that the navigator keeps a more high level view while the
> driver concentrates more closely on the details.
>
> Even when we're not pair programming, we interrupt each other to ask
> questions.  It may disturb one of us, but in the long run, we work more
> efficiently.
>
>
> Kat

Doesn't this result in a very linear approach though, as against working on
different aspects and everyone ending up at the finish point based upon
their set of tasks at roughly the same time?

Phil