Hey Asbjørn, That's a lot of books, and it will t...

2010-02-24T09:39:49.398+01:00

Hey Asbjørn,

That's a lot of books, and it will take a lot of time to cover them all, so without knowing exactly what you want to learn, here's a suggestion for how to go about it:

Read these first:
Pragmatic Programmer - Quick, easy and qood read.
Head First Design Patterns - Much easier to read than DP, and a better place to start.
DP - Again a must read. But it isn't as readable, so it will be heavier. HFDP will cover several core patterns, so you could consider postponing this.
Clean Code - Good read on writing quality code.
PoEAA - First 100 pages or so of PoEAA, briefly look at the rest of interesting patterns. No need to look into the details until you need them.
Domain-Driven Design - Great book. You might consider just reading the quick overview, but you ought to give the full book a go as well. Not quite sure what to recommend given the range of things you want to cover.
Refactoring - Refactoring is important. Ensure you get the principles at least. Don't bother learning the specifics of many of the smaller refactorings, Resharper will help you with lots. Consider having a look at Refactoring to Patterns instead.
xUnit Test Patterns - sure.

Not so much:
Framework design guidelines - Have a look at the TOC, and check interesting sections, but don't read cover to cover.
Working effectively with Legacy Code: You should read it, but don't tackle it first unless you need to tackle large existing legacy codebases
Code Complete - Great book, but it's big, and Clean Code covers lot's of the same topics.

Don't know:
Debugging the Development Process

Comments on Neslekkim's world: Starting from “scratch”, books to read..

Hey Asbjørn, That's a lot of books, and it will t...