I like the attempt at making this process smoother, I guess where to place importance of different aspects relative to each other is always down to opinion and

I like the attempt at making this process smoother, I guess where to place importance of different aspects relative to each other is always down to opinion and interpretation. I wrote this piece a while ago focussing on using the Must/Should/Could principle to speed up the review process and put a less opinionated framework in place to help keep code review moving. https://careerswitchtocoding.com/blog/moscow-the-best-code-review-technique-youre-not-using https://careerswitchtocoding.com/blog/moscow-the-best-code-r... It’s not an original thought from me but many people hadn’t heard about it and off the back of this post I’ve had a few people get in touch to say they’ve implemented it in their team and it’s helped improve code review speed.