We've all been guilty of giving a shallow review: "Looks ok."
Given typical defect densities, any non-trivial design or code is going to contain some errors. Even seemingly trivial maintenance fixes are likely to be defective.
It's your job as a reviewer to find as many of these ...
In "Talent is Overrated", Geoff Colvin at one point discusses how superstars in many fields use the memory technique of "chunking" to boost their short term memory.
His simple example is the 13-letter word "lexicographer". To you and I (assuming you speak English and have a decent vocabulary), it is ...
This is the second half of an article I posted about using a checklist to prevent security errors. There, I said that you have 15 checklist items max, and you shouldn't waste any of those questions on silly things like "Does the code follow the coding standard?".
The 2009 CWE/SANS Top 25 Most Dangerous Programming Errors has been out for a while now. Maybe you've already eliminated all of these errors from your code. In case you haven't, this post will help you develop a checklist that you can use to eliminate these errors ...
Saw this post over at the Project Team Blog Our Projects Are Always Late. Newshirt asks (I'm paraphrasing) "Why would this person not use a time tracking tool?"
Two answers:
Page 1 / 1