Rating: - Average book
Although there are some good insights here and there, not too much to gain.
Rating: - Good book
I am a reader of Balena's books and appreciate his writings. I have read this book and would only say that the objective of the book if not teaching theory to computer science students but to explain practical guidelines.
I am a computer engineering graduate myself and have studied both thoery as well as working on cutting edge technologies for past 7 years.
There are times where most of the theories are not in line with the practical development life cycle and I have seen best of the architects breaking Mr Codds rule on database most of the times.
This book is one such master piece that gives you information on real world development guidelines and best practices and have recommended this book to most of the fresh developers in my team.
- Techie
Rating: - Driven to buy by the negative review
I was driven to buy this book by the negative review of Papadimoulis. I now have the book in my hand, and I haven't been able to put it down.
So far, I haven't seen any recommendations I disagree with. It's actually entertaining to explore the book and discover several tips that I did not really know about. Even the seemingly simple {_string == ""} being slower than {_string.length == 0} was a pleasant surprise.
That elegant and really simple snippet for providing asyncronous support is worth the money I paid for this book. I can already imagine many team mates casually coming by my desk, picking up this book, rifling through absent-mindedly and then suddenly ... wide-eyed with amazement because they just stumbled across a gem.
Rating: - Starts Slow, But Great Stuff
This book has great stuff in it. However, it starts off really slow and might tempt you to skip it. Don't! There is a ton of information for many areas of development. I especially like having both VB and C# and their differences noted. This can be used at any level, but the more experienced reader will value the wealth of knowledge even more.
Rating: - An Excellent Reference
There are few books out there that cover what is sometimes a vague and subjective topic in such a straigtforward and clear manner. I'm always looking for consistent guidelines when constructing code.
No sensible person (ahem, Mr. Papadimoulis) would read this book feeling as though the authors were trying to set their practices in stone. The word "guidelines" is part of the title! Most of the guidelines are accompanied with clear explanations and sometimes exceptions to the rule.
Also, if I may nit-pick for a moment, Papadimoulis (a previous reviewer) states that in the book "they use a class named 'frmMain.'" which is inconsistent with the MSDN. Technically, this is a parameter name that refers to an instance and not the name of a class. I wouldn't even mention this if it were not such a beginner mistake. Especially since the naming guidelines are different.
|