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 ...
This is a rundown of the things you should have in your toolkit -- doesn't matter whether you call yourself a software engineer, programmer, developer, code monkey, etc.
Do time tracking tools have a low uptake because it's tedious to enter your activity data?
What do you use to enter time / activity data into your tracking tool?
If you don't use time tracking, is there a specific reason or is it just not something you've ...
The only good way to create any kind of a reliable estimate is by using (your own) historical data.
If you are trying to create an estimate for a new project and are having a hard time, don't lament your lack of historical data. The best thing you can ...
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 ...