Nov 25, 2009 0
One Simple Step for Avoiding Shallow Reviews
It’s your job as a reviewer to find as many defects as possible. If you’re not finding defects, you’re wasting time.
Read the rest of this entry »Nov 12, 2009 2
Who Else Wants Better Short Term Memory?
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 easy to remember. We don’t have [...]
Jan 27, 2009 0
Five Things That Do Not Belong In A Review Checklist
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?”.
Jason Cohen pointed to an article of his in [...]
Jan 23, 2009 2
How To Use A Checklist to Prevent Security Errors
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 starting at the architecture level and moving through [...]
Read the rest of this entry »Dec 18, 2008 3
Project Team Blog: Our Projects Are Always Late
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:
Because it feels like an extra step. If you want to change a behavior like time tracking, you have to make it automatic. Developers and other project [...]
Read the rest of this entry »
From The Peanut Gallery