I just listened to the latest Hanselminutes podcast: Be a Better Developer in Six Months
Scott Hanselman asks “what are you going to do in the next 6 months to become a better developer”?
He suggest reading books, nerd dinners, having lunches together with other non competitive companies, watch webcasts together during lunch and code reading.
Here is what I am going to do for the next 6 months
I am going to read a technical book every 10 days and review every single book
That should be possible now that my twins are one year old (tomorrow). I have a bit more free time at night to read. Here is the list of books, some of them I have read, some I have partially read.
Code Complete (reread)
I think this is one of those books that you should read once a year.
Practices of an Agile Developer
Some good stuff in here, in ordered it a couple of months ago but did not read it yet.
Inside Microsoft SQL Server 2005: T-SQL Querying (partial reread)
I read several chapters but did not read the whole book.
Inside Microsoft SQL Server 2005: The Storage Engine (reread)
I have read parts of this one; I have read the 2000 edition several times.
I was thinking Design Patterns (GOF) or this one. As you can see I have chosen Refactoring.
Why refactor when you can prefactor? I just skimmed through it in the book store and it looks promising.
Open Sources 2.0
Open Sources 2.0 is a collection of insightful and thought-provoking essays from today's technology leaders that continues painting the evolutionary picture that developed in the 1999 book Open Sources: Voices from the Revolution.
Pragmatic Unit Testing in C# with NUnit
Building the Data Warehouse (reread)
Read this one several years ago, will read it again
Expert SQL Server 2005 Integration Services
Will read this together with the one below at work; have to convert about 60 DTS packages to SSIS.
Microsoft SQL Server 2005 Integration Services
In this unique and insightful book, leading computer scientists offer case studies that reveal how they found unusual, carefully designed solutions to high-profile projects. You will be able to look over the shoulder of major coding and design experts to see problems through their eyes.
Pro SQL Server 2005 Database Design and Optimization (reread)
Read this will read it again
The Art of SQL
Heard some good stuff about this book.
Getting Things Done
We all need some help with organizing our lives.
Getting ThingsDone for the computer person, very useful stuff inside.
Framework Design Guidelines (reread)
Very nice book, you will learn why something was done a certain way. Good tips on what to avoid and what should be done.
New language Book probably Python or Ruby( you decide)
Here is a pic of the books I have at home, the others I have at work or I still have to purchase them.
I will watch 2 web casts a week during lunch time and review those also.
I will look at high quality source code from open source projects and also from the book Beautiful Code. I will go to CodePlex to download a couple of open source projects and will study the source code
I will learn a new language (I actually got this from Ken Henderson who suggests to learn a new language every year) and rewrite one of the current applications in that language. This way I don’t have to worry about logic problems and design, I just have to translate the code.
I will learn a new technology. I am thinking either WCF or WPF
I will keep updates on Pownce (sorry folks no invites left) everyday The reason I am doing this is so that someone can call me out in case I don’t keep my promise. This is similar to stopping smoking but not telling anyone, if you do that then who knows you stopped so that they can confront you?
I know this is cheesy but I will do it anyway, I will tag 5 people I (kind of) know and I want them to tell us their plans.
And I will tag 5 people whose blogs I read but I don’t know them
And you the reader, what will you do in the next 6 months to become a better developer?
Cross posted from here: http://sqlblog.com/blogs/denis_gobo/archive/2007/07/16/1746.aspx