Update [2008-12-31]: I posted the list of code review tools as promised below.

I tweeted this article on Five Reasons to Do Code Reviews from CIO.com last week,and realized that there are much more than the five reasons they give. So I came up with 20 more over ...

Great post on the cost of (not) testing software. The take-home lesson is "find defects early".

The main thing missing from the discussion is that there are better techniques for finding defects than testing. Like design and code reviews, and especially more attention to requirements. Catch defects as early as ...

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:

1. Because it feels like an extra step. If you want to change a behavior like time tracking, you have ...

Here are five reasons you should wait before moving on to the next phase of your software development process:

1. Get the requirements right. It's so often repeated that it's almost a cliché to say that requirements errors will cost 10x or more to fix during coding or testing ...

Joel Spolsky also thinks that using timelog data for performance tracking is a bad idea.