- Series: Developer Best Practices
- Paperback: 240 pages
- Publisher: Microsoft Press; 1 edition (September 12, 2007)
- Language: English
- ISBN-10: 0735624356
- ISBN-13: 978-0735624351
- Product Dimensions: 7.5 x 0.8 x 9 inches
- Shipping Weight: 1.1 pounds
- Average Customer Review: 4 customer reviews
Amazon Best Sellers Rank:
#3,030,084 in Books (See Top 100 in Books)
- #66 in Books > Computers & Technology > Programming > Software Design, Testing & Engineering > Quality Control
- #1070 in Books > Computers & Technology > Networking & Cloud Computing > Data in the Enterprise > Client-Server Systems
- #3174 in Books > Textbooks > Computer Science > Software Design & Engineering
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
I. M. Wright's Hard Code (Developer Best Practices) 1st Edition
Use the Amazon App to scan ISBNs and compare prices.
There is a newer edition of this item:
The Amazon Book Review
Author interviews, book reviews, editors picks, and more. Read it now
Customers who viewed this item also viewed
From the Publisher
Key Book Benefits:
Provides insights into how Microsoft drives excellence in large, distributed, and diverse business groups
Features a foreword by Mike Zintel, Director of Development at Microsoft
About the Author
Eric Brechner, Director of Development Excellence at Microsoft Corporation, has more than two decades experience in the software industry. He began writing “Hard Code” in 2001 as a resource for Microsoft employees. Since then, the opinion column has ignited an ongoing discussion of best practices among the thousands of software development engineers at Microsoft—and now, to the rest of the development community.
Top customer reviews
Because the author was working in the real world you don't get a lot of theory or how things should be, but how thing are, real and unfair. He will defend developers and managers when he thinks they need defending, then turn around and chastised them when he thinks they deserve the criticism. I was a little surprised that while working for large organization and these columns were printed internally in the company, the author did not hesitate to criticize the way management operated.
This is not a boring book. The author has strong opinions, attitudes and does not hesitate to express them on the pages. It is fun to read someone's rants and his justifications for these rants. I'm sure everyone will find something they agreed with and something they will not.
This might sound a little boring, but no--this guy goes for the throat. In understanding that everyone has a specific job to do--and their objectives often oppose those of everyone else--he accurately and bluntly exposes common points of conflict. More importantly, he gives hard-won, actionable advice on how to cut through all that crap and put everyone on the same page.
For managers and architects, this book [namely chapter 1: "Project Mismanagement"] would be a great supplement to two books of Julie Bick's that also offer unique insight: All I Really Need to Know In Business I Learned at Microsoft and The Microsoft Edge.
Another interesting point in this book was the article, "Google: Serious threat or poor spelling?" Here he actually points out the flaws with Google's business strategy and gives tips on how they [or any company] could overcome their weaknesses to become a true competitor to Microsoft.
It's not like he gives up Windows source code here, but don't be surprised if you get a bit anxious reading it...just waiting for FBI agents to break down your door for accessing coveted insider trade secrets.
From mere coding perspective, although this is only touched at high level, both chapter 5 and chapter 6 are inspiring and worth the money of the book, it basically tells that code quality can be predicted and improved, like wise, error handling, duplicated, shared code and data are some of the areas that call for great attention.
The book has been translated into my native language already, but the title is a little misleading, it literally means "The Way of Coding".