I’ve only read the Introduction, which is fairly long for introductions and most people would skip it. I suggest you read it, the book and more importantly the Introduction. The Introduction sort of the reasoning behind the book and for me was part of the reason I will finish the book. If the introduction is any indicator as to the contents of the book, then the stories, the explanations, and the reasoning is enough to justify buying the book. I learned a lot from the introduction alone and expect that had I read the full book that I would have learned a great deal more.
That said, the introduction of the book sort of gave proof and reasoning to a lot of what I’ve been attempting to say at work for how to code. I do not think the author would agree with me completely as the author, from what I could remember, is not as hardline as I was previously with my assertions at work. I do think that this book will be beneficial to me in describing the ideas I could not put in words before for how code should be written and hopefully the rest of the book does a better job of detailing how you should code clean code than say the “Beautiful Code” book that reads more like a book of Fables than a how-to programming book.
I will say that if your viewpoint with coding is GSD (Get-Shit-Done) than it probably won’t flow with your mindset. However, I don’t think the author is that far off from GSD. He even says in the introduction along the lines of it is better to get something done than to put something off to where it never gets done. I interpreted him as to saying that it is better to code something that is somewhat clean and can be made cleaner in the future from simple refactoring than to code it completely terrible and require a complete rewrite. As well as including that it is not wise to dismiss every solution simply because none of them are clean. The primarily job of a programmer is to provide solutions, and to not ideology affect our thinking too much.
Again, this is all from the introduction, so I expect the rest of the book is full of more gems of knowledge and experience. I expect I’ll learn a lot from the rest of the book and I think other programmers will too. Check Amazon for the book.
Possibly Related Posts:
- Bullet: E-Book Library Management and Content Server
- Using ZendFramework 2 beta1 For Directory Project
- The Way of Kings and Cosmere Theory
- “In Time” Movie Premise Flawed
- Completing HTTP Library For PHP
Comments are closed.