Ahh you mean normal programming as I see it, nothing great is achieved with only one programmer in a timely fashion, working as a team is not extreme in any way or fashion, someone there is trying to sound smarter then they are.

Basically programming teamwork is brainstorming on the run, one person does actual inputting and a few people (behind him/her) keep refining and brainstorming over what is the best way to achieve small goals (i.e. displaying data in a easy painless gui)

Really it is just as basic as it is, people working toward a common goal, some people know SQL some know OPP and some know reports it's just a question of who will do the input and who to ask at ever "corner"

when you have multiple people at multiple workstations it gets confusing and a lack of communication grows

Really someone is making this to complex, it's just teamwork, me and my partner do it all the time. A new procedure/function needs to be done, we go over how it should look, act, what data source and what the interface should be like, then we sit down as a team and punch it out, my partner might stop me at a given point and say "Wait I think we should use CASE statements" then we decide one way or the other

To call it extreme is to make it something it is not, programming through time has largely been done in tandems

>Hi Stephen,
>
>Extreme programing refers to a technique whereby 2 programers work on code together as a team. The idea is that each will catch the other's mistakes and refine techniques.
>
>Someone else can jump in with the details of where the concept comes from. One of the programers here introduced the idea recently.
>
>Tim