to comment on the girlscamp discussion. you don't have to name it teams, call it pairs (as discussed in <pair programming>). does it make a difference? no. is it something managament people and business consultants are considering as a method for making more profit? yes. but there is always more to think about than simply saying no or yes. and sometimes it has nothing to do with hindsight. it's more about a value, i wouldn't throw away so easily ...

)) pairs (audio/mpeg, 317 KB)

go back to kindergarten

laurie williams und robert kessler: "all i really need to know about pair <* programming *> i learned in kindergarten

Share everything, Play fair, Don't hit your Partner, Put things back where they belong, Clean up your mess, Don't take things too seriously, Say you're sorry when you hurt somebody while moving furniture, Wash your hands of skepticism before you start, Flush!, Warm cookies and cold milk are good for you, Live a balanced life - learn some and think some and draw and paint and sing and dance and play and work every day some ....

in the end it is getting esotheric, but somehow it is not soo bad. who needs more? mira aqui

keeping it simple, another advicer coming from parc. john seely brown is also talking about storytelling, a principle of collaborative software engineering.