Slashdot Mirror

← Back to Stories (view on slashdot.org)

Are You Too Good For Code Reviews?

Posted by Soulskill on from the what-else-are-end-users-for dept.

theodp writes "Why do some programmers,' asks Chris Hemedinger, 'place little value on code reviews?' This apparently includes even Programming Greats like Ken 'C' Thompson, who quipped, 'we were all pretty good coders' when asked about the importance of code reviews in his work. Hemedinger, on the other hand, subscribes to the school of thought that peer code reviews are Things Everyone Should Do. Not only do reviews keep you on your toes, Hemedinger says, they also 'improve quality, ensure continuity, and keep it fresh. Who can argue against that?'"

4 of 495 comments (clear)

  1. Re:I agree 100% by flooey · · Score: 5, Insightful

    Yes code reviews can be painful especially if you work with some douchebags.

    I don't think the problem there is the code reviews.

  2. I'm not too good for code reviews by jeff4747 · · Score: 5, Insightful

    I'm too busy for code reviews.

    Development schedules are almost always ridiculously compressed. There's no time in the schedule for code reviews. Just like there's no time for thorough testing.

    But the software only has to be 'good enough' for people to buy it, so there's no ammunition for developers to use to get a better schedule.

    1. Re:I'm not too good for code reviews by alexo · · Score: 5, Funny

      Which is pretty much why I gave up on computer science and am moving into Geology instead.

      I heard that Geological processes have pretty relaxed schedules.

  3. Re:Pure Arrogance by MadKeithV · · Score: 5, Funny

    Colleague of mine used to have the following sig: "Write code as if the person who will be maintaining it is a violent psychopath who knows where you live."