On Wed, Sep 28, 2011 at 12:10 PM, Dan Covill <dcov...@san.rr.com> wrote:
> On 09/28/11 06:45, Richard Kaye wrote:
>> Code review? WTF is a code review?
>
> Assuming you're serious, a code review in it's simplest form is just
> having a colleague look at your code.  Big companies make an art form of
> it, with formal meetings etc., but the basis is that a second pair of
> eyes is a great way to spot problems.
>
> I think it's even better if you discuss your code organization and
> strategy with someone else BEFORE you've got it done - easier to change
> and there's less emotional investment.
>
> We always say, "The best way to find a bug is to explain to someone else
> why the code is correct.  If you can't find a co-worker, then explain it
> to the dog.  That works, too."
------------------------

I had a meeting like this last week.

Comments were
"That is a lot of javascript"
Why is there only  <% getData() %> on the webpage?  Where are the controls?


There won't be any more of those meetings.  Sucks for Steve but I had
a difficult time there.



-- 
Stephen Russell

901.246-0159 cell

_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: 
http://leafe.com/archives/byMID/profox/CAJidMYJTJcwEi5WmbFBbsox4uAUy8n=bcpvczfd7x9wyoes...@mail.gmail.com
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.

Reply via email to