I recently received an email from a Head First reader suggesting we consider creating supplemental Head First reference books for the existing titles in the series: materials that would presumably provide a summary/recap of key concepts and skills covered in the books that readers could quickly refer to as needed.
I'll admit, the idea of HF reference books had never occurred to me, but I can see how many folks would find them useful. HF books are amazing learning tools, but what happens when you've finished reading, say, HF JavaScript or SQL, and just want to refer back to the main specs on the XMLHttpRequest object or the SELECT statement? In our books, the key details on the syntax, parameters, implementation, etc., may be spread out over several pages and couched within narratives and other teaching devices we use like Fireside Chats and No Dumb Questions. In other words, HF books are far from ideal as reference books.
And this is not unintentional on our parts. Back at the inception of the HF series, a decision was made to make the books learning books, not reference books. To quote series co-creator Bert Bates (see our November newsletter for the full interview with Bert from which this is excerpted):
We realize that in many cases HF books make poor reference books. We decided in the beginning that we would focus completely on learning, not on reference. It might be possible to create a single book that does a great job of teaching a topic AND being a reference guide for that topic, but we felt that we’d have better success if we focused our efforts purely on teaching.
So, HF books will always be first and foremost geared toward teaching, even if that means sacrificing some of the value inherent in presenting topics in a more reference-y format. After all, it's our teaching style, the way we "Make It Stick" in your brain, that's the main appeal of the books, right?
That said, I'm curious to hear the thoughts of some readers out in HF Land. When you're done reading HF books, do you use them as reference books? Or do you find them ill-suited to this purpose? Are there other wonderful reference books you've found that make great companions for the books in the HF series? Would you be interested in supplemental HF reference materials to go hand-in-hand with the books?
Share:
As I go through a HF book i use those file tabs to label main points in the book that I might go back to later. It seems to work well enough for me.
However if there were a supplemental reference for each HF book that was done right I'd most definitely buy it!
As you know Sanders, from my email address not the pseudonym, I was the one that wrote the email. First, do not change a thing with the HeadFirst books. They are truly the best books bar none. Having said that I will paraphrase what you wrote, the great nuggets of insight are hidden in the graphics, sidebars, boxes, etc. For example in the C# book it shows what a constructor looks like, why it is a constructor and not just another method. Then scattered around the page and across pages additional insights are offered. I underlined all the different points in order to know for sure I understood the concepts. Eventually I will create my own reference book by writing the underlined notes in a loose leaf book. In other words in addition to reading , studying and then doing the examples I then write down the important points and this takes an enormous amount of time. If I have the time I may even type it in Word.
My take, create a reference book that has a smaller footprint with around 50-60 pages. Have it include short examples and then define each area of importance. Also reference the page to the headfirst book. I believe we really need a reference book for the purpose of converting the learned knowledge gained by reading the HeadFirst books to the applied knowledge of programming.
Unsolicited plug
The books are beyond great, I write a question in the forum and the author replies, I write to you on New Year’s day no less and you respond back in around 1 1/2 hours. What is going on? Is this a group of people that truly believe in what they are doing and care about the people that buy their books? You guys are amazing. I have only one very big complaint. Where were you guys ten years ago? I love these books and knowing everyone in your organization stands behind the HeadFirst books makes me feel really good about purchasing your books.
Personally, I would prefer that you guys stay focused on what you do well for a little while longer. Once there's enough of a dedicated staff and books are being regularly churned out, maybe... but no one does what you do well, if at all. There are TONS of reference books. If you have any points of innovation to the reference model, then cool, but I need PHP & MySQL, AJAX, XML, ALGEBRA, PHYSICS, and Web Services books before you guys get potentially bogged down with a new product concept.
I do go back and reread parts of my HF books quite a bit. And like headfirstfan, I also keep notes, summarizing what I learned in a particular section. True, the format of the book does make it is a little difficult to use as a reference. I sometimes wish that there was a summary of points at either the end of each chapter or at the end of book in an appendix. But I like the idea of a supplemental reference book with short examples - you have my support and $$$!
I also agree with Samuel Allen. Don't delay the long anticipated books in order to develop reference books. On the other hand if the authors that have written books are not involved in new projects then this would be a nice follow up to their work.
I personally believe the work will be far less difficult to produce. Most of it can be copy/paste with possibly some additional commentary.
It would be quite handy to have a few pages of reference section at the end of each book with the key things covered. It is frustrating when you remember something is in one of the books and it's not something you can just look up in the index so you then end up having to read through half the book to find it!