Junilu Lacar wrote:
Interesting. I do exactly the opposite for code reviews I conduct. My thinking is that bugs should be address by unit testing. Team level code reviews are for ensuring everyone who looks at the code comes to the same understanding of its intent. That often doesn't happen when code is not expressive and readable.
In my book, bugs are caused by misunderstanding. If you focus first on bugs without making the code readable and understandable, then you are ignoring the root of the problem.
Liutauras Vilda wrote:Are these related to some extent?
https://coderanch.com/t/714433/code-reviews/engineering/Experiment-Code-Reviews-GitLab (from 6 days ago)
Liutauras Vilda wrote:
https://coderanch.com/t/697113/open-source/Automation-Modern-Code-Review (from 27 July 2018)
And I'm sure I saw more of this kind from even earlier times.
Brecht Geeraerts wrote:Since I have a PhD myself, I have always been intrigued by academic scientific research. On the site it is stated that the participants need to stay focussed until the end for the data to be valid. Based on what objective criteria will you include/exclude data to limit the bias in your study? i'm just curious...
Carey Brown wrote:I would prefer to see all the questions first before committing to spending the time answering them.