> One could argue that if you have to discuss these very deep topics in a PR, you better had brought them up before coding that stuff wrong in the first place.
Fair point, and 100% on the nose. The times when this comes in handy is when you have to PR on a project you don’t know a lot about (which could be argued is a process problem, but I am getting way off trail now).
However, with your excellent point in mind, I am even more confused on what a “culture of rigorous code reviews” is.
Fair point, and 100% on the nose. The times when this comes in handy is when you have to PR on a project you don’t know a lot about (which could be argued is a process problem, but I am getting way off trail now).
However, with your excellent point in mind, I am even more confused on what a “culture of rigorous code reviews” is.