tag:blogger.com,1999:blog-19518771.post406711016129575707..comments2022-11-09T11:48:56.095+01:00Comments on Neslekkim's world: Starting from “scratch”, books to read..Neslekkimhttp://www.blogger.com/profile/11469025865014384914noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-19518771.post-20937040669957164632010-02-24T09:39:49.398+01:002010-02-24T09:39:49.398+01:00Hey Asbjørn,
That's a lot of books, and it wi...Hey Asbjørn,<br /><br />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: <br /><br />Read these first: <br /><b>Pragmatic Programmer</b> - Quick, easy and qood read.<br /><b>Head First Design Patterns</b> - Much easier to read than DP, and a better place to start. <br /><b>DP</b> - 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.<br /><b>Clean Code</b> - Good read on writing quality code. <br /><b>PoEAA</b> - 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. <br /><b>Domain-Driven Design</b> - 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. <br /><b>Refactoring</b> - 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. <br /><b>xUnit Test Patterns</b> - sure. <br /><br />Not so much: <br /><b>Framework design guidelines</b> - Have a look at the TOC, and check interesting sections, but don't read cover to cover. <br />Working effectively with Legacy Code: You should read it, but don't tackle it first unless you need to tackle large existing legacy codebases<br /><b>Code Complete</b> - Great book, but it's big, and Clean Code covers lot's of the same topics. <br /><br /><br />Don't know:<br /><b>Debugging the Development Process</b>Rune Sundlinghttps://www.blogger.com/profile/10334374587401199926noreply@blogger.com