Interview: Author David Black

Our Book Promotion: “The Well-Grounded Rubyist” starts today. Win one of four books to be given out for active participation. The coolest thing? Author David A. Black will be on site to answer questions! Click here for more details. Here, in this brief interview, Satish Talim of RubyLearning talks to David A. Black.

David A. Black

Satish>> David, could you tell us something about yourself – your background, where you are based?

David>> I’m from Connecticut originally, and I live in New Jersey. My first computer programming experiences were with a PDP-8 and PDP-10, in the early 1970s. I was thirteen years old, and in those days, unlike today, a thirteen-year-old programmer was a rarity! I didn’t do much with computers in later years until the late 1980s, when I got my first PC and gravitated to programming again. Meanwhile, I was starting an academic career in a different field, and taught college from 1992 to 2005. I then made the decision to leave the university and devote myself full-time to Ruby and Rails development, training, and writing.

The Well-Grounded Rubyist

Satish>> Who’s the audience for your book – The Well-Grounded Rubyist? Does it teach Ruby programming or is it a reference book?

David>> The Well-Grounded Rubyist is for programmers who are new to Ruby, as well as people who have done some work with Ruby and now want to learn it more deeply and systematically. It’s definitely a teaching book rather than a Ruby reference work — not that it doesn’t cover lots of language features and techniques, but its purpose is to bring you to a deep understanding of how things work in Ruby, and to give you the foundation you need for a long-term, ongoing relationship with the language.

I think of myself as having switched careers from teacher to computer programmer, but at the same time, there’s definitely a teacher part of me that’s always there. I love explaining things to people and helping them “get it”, and writing a book like this is the perfect way to combine my programmer and teacher sides. That’s also why I do a lot of Ruby and Rails training, and why I truly enjoy it.

Satish>> How different is this book from your other book – “Ruby for Rails”?

David>> TWGR is what I have described as a “repurposing” of R4R. Of course the main difference is that TWGR doesn’t talk about Rails. But it also covers a lot more of Ruby, and brings it up to date by focusing on Ruby 1.9.1.

In working on TWGR I’ve drawn on material from R4R, but everything has been revisited, revised, and updated. There was no automatic cut-and-paste from R4R. It was important to me for TWGR to stand entirely on its own — and the fact that it’s about a different version of Ruby, as well as being more inclusive, reinforced that need.

In fact, when I started working on TWGR I thought it would be easier than it turned out to be. Just take out Rails, add some new material, update everything, and there it is! It turned out to be much harder than that, and it took longer than I expected. But that turned out to be a blessing in disguise, since the book’s appearance has coincided nicely with Ruby 1.9.1, the first stable version of Ruby 1.9.

Satish>> I know that it is too early to say, but looking back are there some topics that you now wish should have been covered or dropped from the book?

David>> Nothing so far, though as you say it’s still early :-) There’s always judgment involved in choosing topics and deciding what to emphasize. My guiding principle has been to try to leave the reader in a position where, even though there’s more to learn, there won’t be any big surprises: everything you learn about Ruby later on will relate in some way to what you’ve learned in the book.

Satish>> Anything else you would like to add?

David>> Only to thank you for inviting me to talk about the book, and that I hope everyone learns from it and enjoys it!

Thank you David. In case you have any queries and/or questions, kindly post your questions here (as comments to this blog post) and David would be glad to answer.

comments powered by Disqus