Ricardo

66%
Flag icon
Never look at the commit history during a group code review. Focus on changing the future, not on dwelling on the past. • Comments should be objective and constructive. The focus is on how to make the code better and not to say why it sucks. • Sometimes having a facilitator helps. Her role is to make sure everyone speaks and that there is no fingerpointing.
Software Craftsman, The: Professionalism, Pragmatism, Pride (Robert C. Martin Series)
Rate this book
Clear rating