Testing the boundaries of collaboration
Two experiments that break the rules succeed spectacularly. Lessons learned from the Limbo model - of tiny changes, instantly deployed - can pave the way for real-time software development collaboration.
- Small changes are usually safe, so roll them out straight away and save the slow, costly code reviews for the small percentage of riskier, bigger changes that really need them.
- Try a test, commit, revert (TCR) workflow where you create a little commit every time a test passes—and deleting changes if the test fails. The automatic erasure of mistakes incentivizes you to make your changes smaller—and less likely to fail.
- Collaborate in teams using the Limbo model and your collaborators may be supplying corrections for your mistakes even without knowing what you were doing.
Full post here, 9 mins read