Commit-then-Review 1998
Improving the development experience (again)
- fragmentation of primary developer time
- disjunct between reviews and working time
- imbalance of contributions
Lazy consensus when consensus is likely
- commit changes first and review based on logs
Automate some administrative actions
- status in CVS, posted every other day
- open PR summary posted once a week