We’re a group of a bit over 10 programmers at Nelen&Schuurmans. Coordination and quality and interaction is something you’ve got to watch carefully with a group of that size.
I’d like to mention one item that’s we’re using more and more: github pull requests. One programmer works on a branch and then submits a pull request so that others can look at it.
@cached_propertyin one of my pull requests. I got to explain it and he learned something useful. In the same way, I keep learning things myself.
How did we get it started? Someone suggested it in a team meeting and started using it himself. And actively shopped around for others to review his code. This way it immediately became the norm for that individual package and others started to join in.
In the week after, a project started with three programmers. They agreed on “doing it with pull requests” and stuck to that decision. Three more converts! Each of them now regularly use it in other projects, too, taking even more developers down the Righteous Path of Pull Requests.
The core reason why it spreads, though: pull requests work great. Quality improves, everybody learns more, knowledge spreads, etc. Nice!
My name is Reinout van Rees and I work a lot with Python (programming language) and Django (website framework). I live in The Netherlands and I'm happily married to Annie van Rees-Kooiman.
Most of my website content is in my weblog. You can keep up to date by subscribing to the automatic feeds (for instance with Google reader):