What really is important to get past code review? A lot has been said about good tooling, and good practices. This is a slightly meta-look at why I think we do it all in the first place.
Great first post. This really resonates with teaching lesson planning to beginner teachers and more experienced teachers alike, especially these two points:
- Make documentation accessible. Ask yourself: If the change author is not around, would someone be able to recover a failure by just following the documentation?
- Small changes inspire confidence. Breaking down a change into small logical steps is a skill that not everyone possesses, but it is learnable. Making changes progressively over multiple stages allows the author to build confidence and reduce the risk of failure.
Great first post. This really resonates with teaching lesson planning to beginner teachers and more experienced teachers alike, especially these two points:
- Make documentation accessible. Ask yourself: If the change author is not around, would someone be able to recover a failure by just following the documentation?
- Small changes inspire confidence. Breaking down a change into small logical steps is a skill that not everyone possesses, but it is learnable. Making changes progressively over multiple stages allows the author to build confidence and reduce the risk of failure.
Look forward to the next installment!