News:

Holy shit, it's 2018 2019 2020 2021 2022 2023 2024, and the US isn't a fascist country! What a time to be alive.

Main Menu

truth about code review's

Started by Lead, August 27, 2008, 01:25:58 PM

Previous topic - Next topic

0 Members and 6 Guests are viewing this topic.

Lead



QuoteSon, if you really want something in this life, you have to work for it. Now quiet! They're about to announce the lottery numbers. - Homer Simpson

iago

Agree.

Wait, that domain is blocked at work, so all I see is a 'X' :)

Camel

Quote from: iago on August 27, 2008, 02:09:47 PM
Wait, that domain is blocked at work, so all I see is a 'X' :)

Top:
The only valid measurement of code quality: WTFs/minute

Left:
Door labeled "code review" with two speech lines coming from it with "wtf" at the end. Below the door is the annotation, "good code"

Right:
Same as left, with extra more "WTFs," and the annotation reads "bad code"

<Camel> i said what what
<Blaze> in the butt
<Camel> you want to do it in my butt?
<Blaze> in my butt
<Camel> let's do it in the butt
<Blaze> Okay!

Hdx

Agree, But its sad most the code I deal with goes on the right.
http://img140.exs.cx/img140/6720/hdxnew6lb.gif
09/08/05 - Clan SBs @ USEast
[19:59:04.000] <DeadHelp> We don't like customers.
[19:59:05.922] <DeadHelp> They're assholes
[19:59:08.094] <DeadHelp> And they're never right.

Sidoh

I don't think I've ever attended a formal peer review.

At work this summer, we had "inspections", but the process was much more well-defined.  Reviewers would mark defects before the meeting independently, the person would either fix them or make a comment saying the issue should be discussed during the meeting.  It kept out the long, drawn out debates that result in pretty much nothing.  It was a fairly painless process.  The meeting for my code, which was about 10k lines, only took 45 minutes -- and that was with the principle engineer there. :)

iago

Quote from: Sidoh on August 27, 2008, 08:18:07 PM
I don't think I've ever attended a formal peer review.

At work this summer, we had "inspections", but the process was much more well-defined.  Reviewers would mark defects before the meeting independently, the person would either fix them or make a comment saying the issue should be discussed during the meeting.  It kept out the long, drawn out debates that result in pretty much nothing.  It was a fairly painless process.  The meeting for my code, which was about 10k lines, only took 45 minutes -- and that was with the principle engineer there. :)
Heh, we had something similar at Symantec, where the document I wrote would go to an editor, then come back for changes, then we'd discuss it all. But, there was one difference -- you weren't allowed to argue with the editor, no matter how wrong he was (especially when it came to technical stuff). I tried to decline a change once, and he came to my desk to yell at me (even though he was clearly wrong, to the point where somebody changed it back during the final review.. justice! :) ).

Sidoh

Yeah, I suppose that sort of makes sense since its his job to correct, pretty much.  The meetings we had were all engineers and the occasional manager who was mostly there to make sure everyone was working, lol

Joe

Quote from: HdxBmx27 on August 27, 2008, 07:51:19 PM
Agree, But its sad most the code I deal with write goes on the right.

:)
Quote from: Camel on June 09, 2009, 04:12:23 PMI'd personally do as Joe suggests

Quote from: AntiVirus on October 19, 2010, 02:36:52 PM
You might be right about that, Joe.


Hdx

Quote from: Joe on August 30, 2008, 04:47:52 PM
Quote from: HdxBmx27 on August 27, 2008, 07:51:19 PM
Agree, But its sad most the code I deal with write goes on the right.
:)
I'm getting better.
And 90% of the WTF?s are because I don't comment. AT ALL.
http://img140.exs.cx/img140/6720/hdxnew6lb.gif
09/08/05 - Clan SBs @ USEast
[19:59:04.000] <DeadHelp> We don't like customers.
[19:59:05.922] <DeadHelp> They're assholes
[19:59:08.094] <DeadHelp> And they're never right.