How do the experts solve difficult problems in software development? In this unique and insightful book, leading computer scientists offer case studies that reveal how they found unusual, carefully designed solutions to high-profile projects. You will be able to look over the shoulder of major coding and design experts as they work through their project's architecture, the tradeoffs made in its construction, and when it was important to break rules.

In the space below, I've gathered some pointers you can follow to learn more about the contributors to this anthology.

Regular Expressions, by Brian Kernighan

Karl Fogel, on the Delta Editor in Subversion

Jon Bentley, author of Programming Pearls

Conversation between Tim Bray and Jim Gray

Elliotte Rusty Harold

Michael Feathers on Fit: Framework for Integrated Test; see his paper, emergent optimization in test-driven design

Alberto Savoia, one of the InfoWorld CTO 25: "We want to do for software quality what Google has done for search quality." See Testing Genes, Test Infection, and the Future of Developer Testing:

Some developers are easily test-infected - they take to unit testing like a duck to water. Others need some time and encouragement, but eventually "get it". A third group appears to have immunity to test infection. I invent a test-gene model to categorize these groups and look at its implications for the future of developer/unit testing.

Charles Petzold; here he is on Joan Didion and the play version of “The Year of Magical Thinking”.

Top Down Operator Precedence, by Douglas Crockford

Henry Warren, author of ... [ Read More (1.1k in body) ]