I think as you said that bug tracking and source control are more important than code reviews, but for a company who has these (and all that wite software should) then code reviews are a great way to increase team involvement and build quality. Good talk. Thank you.
I think as you said that bug tracking and source control are more important than code reviews, but for a company who has these (and all that wite software should) then code reviews are a great way to increase team involvement and build quality. Good talk. Thank you.
I've been pushing for code reviews at work. Patrick gave some great examples to help in my argument. It's getting the old school programmers to see the true value.
Good content....might have been a bit too much of it on the slides though. Agreed on the other comments that the presentation was a bit dry. The cute kid picture was nice though :) (maybe there's a market for kids doing fuzz testing hehe)
Great talk overall, but I would have enjoyed some more examples of what actually *doing* the code review was like. I don't know, something like a chunk of code that was 'in review' and then hear Patrick's thoughts on it and the types of things he'd be looking for and what he'd comment on, etc.
Comments
Comments are closed.
I think as you said that bug tracking and source control are more important than code reviews, but for a company who has these (and all that wite software should) then code reviews are a great way to increase team involvement and build quality. Good talk. Thank you.
I think as you said that bug tracking and source control are more important than code reviews, but for a company who has these (and all that wite software should) then code reviews are a great way to increase team involvement and build quality. Good talk. Thank you.
Good overview of the whats and whys of code reviews.
Subject matter was a little dry, a few more interjections of humor would really help to keep attentions focused.
Good overview of the workflow that can be used to do code reviews and why it is important.
I've been pushing for code reviews at work. Patrick gave some great examples to help in my argument. It's getting the old school programmers to see the true value.
The code review workflow examples were good.
A bit dry. The material did provide a good overview, without providing any magic "bullets".
Was a bit slow paced without enough audience interaction.
Good content....might have been a bit too much of it on the slides though. Agreed on the other comments that the presentation was a bit dry. The cute kid picture was nice though :) (maybe there's a market for kids doing fuzz testing hehe)
Great talk overall, but I would have enjoyed some more examples of what actually *doing* the code review was like. I don't know, something like a chunk of code that was 'in review' and then hear Patrick's thoughts on it and the types of things he'd be looking for and what he'd comment on, etc.