Comments on: Code review challenges that slow down your productivity https://www.michaelagreiler.com/code-review-pitfalls-slow-down/?utm_source=rss&utm_medium=rss&utm_campaign=code-review-pitfalls-slow-down Sun, 08 Jan 2023 13:18:09 +0000 hourly 1 https://wordpress.org/?v=6.1.6 By: Dr. Michaela Greiler https://www.michaelagreiler.com/code-review-pitfalls-slow-down/#comment-938 Tue, 30 Jul 2019 07:20:29 +0000 https://www.michaelagreiler.com/?p=784#comment-938 In reply to Christoph Rissner.

Thank you! I’m glad it resonates with your experience.

]]> By: Christoph Rissner https://www.michaelagreiler.com/code-review-pitfalls-slow-down/#comment-928 Mon, 29 Jul 2019 20:18:13 +0000 https://www.michaelagreiler.com/?p=784#comment-928 Having done code reviews for oh-so-many years, this is a nice writeup about pros and cons.
Thanks!

]]> By: Dr. Michaela Greiler https://www.michaelagreiler.com/code-review-pitfalls-slow-down/#comment-104 Tue, 30 Apr 2019 05:23:08 +0000 https://www.michaelagreiler.com/?p=784#comment-104 In reply to h.alex.

Yes, I am a big fan of pair programming. I think it is really powerful if used in the right situation, like a complex decision or difficult algorithms.
Also if you consider over the shoulder code reviews the distinction between code reviews and pair programming can become blurry. Over the should review is an informal way of code reviews where you ask a colleague to look at a some part of your code and give feedback. Sometimes this then results in a pair programming session.
The major drawback of pair programming is that if one developer can easily program and solve the problem, the other developer is in a sort of idle state.
From a productivity standpoint, it is more overhead than doing code reviews. Personally, I highly value pair programming when I am confronted with something complex that needs input from a colleague.
But after a while, I am very happy to just go on with my work by myself.

]]> By: h.alex https://www.michaelagreiler.com/code-review-pitfalls-slow-down/#comment-99 Mon, 29 Apr 2019 07:26:04 +0000 https://www.michaelagreiler.com/?p=784#comment-99 What about pair programming as code review method? From my point of view, pair programming brings lots of the benefits of traditional code reviews like knowledge transfer, code improvements, alternative solutions and so on but avoids some of the problems like “time-aligenment” between developer and reviewer, large reviews, too less information about the motivation of the code change etc..
Or are there significant drawbacks of pair programming compared to code reviews?

]]>