I recently had a book published through Packt Publishing titled Instant RSpec Test-Driven Development How-to.

The book is targeted at novice to intermediate software developers who want to quickly become productive with test-driven development methodology (TDD). I don't dwell much in theory, instead delivering compact how-tos and practical examples, though admittedly the book's length - very short, at just around 50 pages of actual content - precluded any advanced refactorings or some of what I consider more interesting features of RSpec.

While most of the material you could figure out how to do by reading a plethora of online articles - though sorting out what's recent and up to date versus what's old and deprecated could be a little challenging - I think the short, concise format packs a good value for its price. In fact the hardest part about writing this book was cutting back on the word count and making each sentence as concise as possible while still maintaining readability.

The actual authoring of the book was a decent experience as I found the reviewers and editors from Packt were very helpful and communicative through the entire process. The only issue I had was having to use a WYSIWYG editor, primarily for the change tracking feature, and I used Pages (on OSX) while the rest of the editing team was using Microsoft Word. I hope that Github provides tooling necessary to replace these sorts of editors, especially for technical books where code samples can be pulled right into the manuscript - I know its something they've mentioned that is on their radar. (The final product, layout, etc. was nothing like what I saw in the WYSIWYG - Packt did a bang up job of layout and formatting.)

The coolest thing? Having copies of the physical book in my house.