Amazon Reviews

5.0 out of 5 stars Add this one to your bookshelf!, February 29, 2008

By David Taylor “airwave”

Excellent book! Real-to-life, creative thinking, lessons build upon themselves as you go through the book. It mirrored some of the things I’ve been through during 20+ years of HW/SW debug and Customer Support roles. I HIGHLY recommend this book and feel it should be required reading either during school or as new employees in relevant positions. [Permalink]

5.0 out of 5 stars A new method and style to write engineering books, August 3, 2007

By Carlos X. Rosado “Carlos X. Rosado”

Very intriguing book that reveals some of the experiences of young engineers in the field. It is a good guidance that takes you by the hand walks you through struggles, and shares some of the common frustration feelings that the engineering carrier exposes you to. It ought to be read by students who are hesitating about studying engineering and recently graduates that do not know what to expect from the field. The book itself is more than a text book and should be considered as an alternative to write engineering books. I really enjoyed trying to solve the mysteries while I was reading. [Permalink]

5.0 out of 5 stars Refreshing and Welcome, January 10, 2009

By Riley Cooper

“…Phone on Fire” is a refreshing and welcome departure from how embedded systems are treated in other books. The author brilliantly creates a team of real-world characters, warts and all, caught in a whirlwind of enormous technical challenges, impossible schedules, inadequate funding, questionable management, internal strife, avoidance of responsibility, harassment, and irate customers. This is the kind of stuff not taught in school. With all this melodrama, you may think this is not a technical book. But it is; the author weaves into the story numerous technical problems the team must solve. She builds suspense by also inviting the reader to try solving them. It’s all about finding and fixing bugs.

This book is a must-read not only by embedded systems engineers, but also by their managers and other groups in an organization responsible to design, develop, test, produce, and support embedded system products. It’s one of those “couldn’t put it down” books. It’s an easy read; the author knows how to reach her audience in a thoroughly understandable way. [Permalink]

5.0 out of 5 stars Loved it!, August 14, 2007

By Carol S. Lewis “Movie buff”

I loved reading this book. I learned a lot about debugging and thought the “novel” (in both senses of the word) format was great. In addition to being a good engineer, the author handled the characterization and plot lines very well. As an E.E. and also a big fan of reading mystery novels, I thought it was a satisfying and unique experience to do both at once! It’s so rare that the insider view of what being an engineer is like is presented like this–the emotional content of being an engineer and being faced with the kinds of problems that come up every day. My hat’s off to the author! [Permalink]

5.0 out of 5 stars Not just for embedded programmers, 17 Sep 2008

By Geek Lady

The title made me read this book but the way it’s written meant I couldn’t put it down. The strategies in this book could apply to any type of programming so if you’re not an embedded coder don’t be put off. The code was not familiar to me but were simple enough to follow with my development background. Investigation and problem solving techniques don’t come naturally to all and I’m sure that this book could assist and inspire many programmers. [Permalink]

5.0 out of 5 stars Enjoyable embedded system bug detection, 10 Jun 2007

By M. Ansdell-Smith

Presents a series of problems faced by members of a fictitious team of embedded developers writing and fixing code for a variety of devices. The book gives the reader opportunities to review the relevant symptoms and code to diagnose a variety of problems in advance of the solution being presented and explained. Enjoyable and instructive. [Permalink]