"Set aside some money and buy this book, or get a friend to buy it and get it from them while still in the store. When you get home, read it TWICE so that you master what is in these pages. Then read it again."
—DevCity, September 24, 2006 (Read more)

Sample chapter reprinted
—LinuxWorld, August 24, 2006 (Read more)

"The cost and the benefits descriptions of the different programming statements is this book's value . . . While the author claims not to 'teach anything revolutionary,' high-level programmers beyond novice should consider Randall Hyde's opinions."
—Unix Review, August 26, 2006 (Read more)

Contributed article by Randall Hyde entitled, "The Fallacy of Premature Optimization"
—ACM Ubiquity, June 27, 2006 (Read more)

"This is one of those books that most serious software developers should have sitting on their shelves."
—Duffbert's Random Musings, June 25, 2006 (Read more)

"This second volume in the series describes methods for choosing high-level language (HLL) statements to create the most efficient machine code when using a modern optimizing compiler."
—Book News, June 2006 (Read more)

"What I did like about this book is the plethora of options that are presented."
—Electronic Design, June 6, 2006 (Read more)

"Exceeds its goal of helping developers pay more attention to application performance . . . a must for any high-level application developer."
—Free Software Magazine, May 9, 2006 (Read more)

Book excerpt posted; "As a high-level-language programmer, if you want to know what's really going on with your programs, you need to spend a little time learning assembly language—and you won't find an easier introduction."
—DevX, April 14, 2006 (Read more)

"It would be an understatement to say [Hyde] has a good handle on this subject . . . Readers who are experienced developers with a genuine interest in writing quality code will get a lot out of this book."
—WithAT, April 14, 2006 (Read more)

"This is a good book. A very very good book. Frankly, I'm blown away at the quality of writing."
—Toronto Ruby User Group, February 22, 2006 (Read more)