On some Agile teams pair programming is the norm; developers enjoy the collaboration and experience enhanced productivity. Others, though, work on teams where pairing is shunned, avoided, or just faked. Why do some craftsmen thrive with pairing while others want nothing to do with it?
“Why should we write our tests first? Isn’t that going to slow my development?” “What? Assigning a single task to 2 developers? How is that efficient? What a waste of resources!” “Look, in the perfect world your advises are great, but I have a project to finish here.” In this …
This short tutorial explains Pair Programming of Agile Scrum Development and why Pair Programming is such a good idea. It dives into the reasons why we should use Pair Programming including: built in peer review, better thought out code and better knowledge sharing.
What is pairing all about? Is it only about writing code or tests, or is it more than that? Come have some fun and learn how to pair without writing code. You might even find yourself laughing and making friends.
Pair Programming is a core practices of extreme programming and literally means that all production software is written by two programmers, sitting side by side, at the same machine. This practice ensures that all production code is reviewed by at least one other programmer, and results in better design, better …
Saros is an open source Eclipse plugin for distributed pair programming. It allows to do collaborative text editing with support of many participants at once. All members of a session have an identical copy of an Eclipse project and Saros keeps these copies synchronized. http://www.saros-project.org/DemoVideo
