Phone on Fire Newsletter, Issue 1
Friday, October 20th, 2006 | Author: lisaksimone


Welcome to a very very occasional newsletter about my upcoming book, “If I Only Changed the Software, Why is the Phone on Fire? Debugging Methods Revealed in Technical Mysteries for Engineers.” If you want to be removed from this list, reply and tell me to Take a Hike. No Problem.

Why are you receiving this email? I have included each you for one of several reasons. You might have replied to the “test case” publication, “A Feynman Approach to Debugging” in Embedded Systems Design in 2004. You may have helped with the book in some way, or been an inspiration for one of the characters. Or you may have survived with me through similar situations in the real world. Or you asked to be kept up to date on the production process. I really hope you enjoy the final product!

“Phone on Fire” contains a series of technical mysteries for readers to solve, with the underlying goal of teaching effective debugging and problem-solving techniques. Stuff that you need in the real world, but you don’t get in college. It’s fiction, and it’s nonfiction. Meant to be more fun than a textbook. “CSI for Embedded Systems” if you will. “Law and Order for Engineers.”

Each mystery is solved by the fictional team of developers from Hudson Technologies. They’re a typical engineering team that is faced with recognizable management problems, insane customers, crazy deadlines, and products behaving badly. Each mystery is also accompanied by a Real World Bug, courtesy of Jack Ganssle and his collection of embedded systems disasters.

The book will be available in March 2007, published by Elsevier, and will premier at the Embedded Systems Conference in San Jose, the week of April 2, 2007. I’ll have a book signing - would be great to see you there!