Ian Langworth and I wrote this book to show dozens of different scenarios for testing software with Perl. We used the Developer's Notebook format, which presents a lab, shows some example code, and then explains it. It's like sitting with a good Perl tester who walks you through working code. (It's not just for testing Perl code; we show how to use Perl's testing tools to test everything else.)
Powell's | Barnes and Noble | Amazon
This little book grew out of a conversation that Tim O'Reilly and I had at OSCON in 2002. It took too long to write, but I'm always glad to hear people tell me that they've bought copies to give to their customers or managers. It was also a real thrill to have Ward Cunningham write such a nice preface.
Powell's | Barnes and Noble | Amazon
This is the first book I ever had published. Slash didn't take off as a piece of software as much as we thought it would, but I stand by the book as useful for its discussions of how to build a successful community online, both technically and socially. I still keep writing about the subject.
This is another project the Hacks group let me do, knowing that I have a strong interest in games. Simon showed off his knowledge and capability from his first proposal and outline and I'm glad to have shaped the book. Incidentally, I put a photo of my nephew in one hack and the first actual serious Python program I ever wrote in another.
Powell's | Barnes and Noble | Amazon
I've had the privilege of working with Dru Lavigne ever since I started working for O'Reilly. When the idea of BSD Hacks came up, I immediately knew that she was the right author. Then the Hacks group offered me the chance to edit the book. It turned out well.