I stumbled across an very interesting article from Jacob Kaplan-Moss on my twitter feed, where he describes a very nice technique for software engineers (and others as well) how to make better estimates for your work.
Especially for young developers estimates are always a hard thing. While they can also cause a lot of frustration, if they don’t work out as expected. Nether less, they are an very important part of commercial software development. So you have to get your way around them. Over the years I developed a quite similar approach by trail and error, without ever thinking about it. So it was fascinating to see such a nice and clear write up of these technique. On that note, if you are into project management & planning give his other articles a read as well ;)