If you haven’t ever come across any of the books in the Sams Teach Yourself <Insert Technology> in 24 Hours, the idea behind them is this: Each chapter can be read in one hour, and there are 24 chapters in the book. Therefore you can theoretically complete the book in a total of 24 hours. While some people may be misled into thinking that they’ll learn what they want in a day, it’s really just a clever gimmick — and for the most part, it works.
In reality, I’ve become a bit of a fan of this technique. Much of the writing style revolves around the idea that each chapter should be taken one hour at a time, and breaks can be taken whenever you need to. More often than not, the chapters don’t take an entire hour and you can complete the book in much less time than 24 hours total.
Naturally there were things I liked about the book and things I didn’t like so much. To be honest, the things that bothered me a bit were because I was being very picky about the subject.
Luckily, from the opening of Sams TYJS, caution is given towards writing code that is cross-browser and more importantly unobtrusive. I was impressed at the mention of such phrases as “graceful degradation” and “progressive enhancement”. I was also very impressed in regards to some of the detail the author touched upon when talking about common differences a developer will run into when testing on various browsers. The author also gives some good beginner tips to first time programmers when speaking about avoiding broswer-specifc code, writing good documentation, and taking usability and accessibility into account when writing scripts. Throughout the book the author mentions the benefits to separating the structure, presentation, and behavior of a document. It’s great to read these things in such books that are quite likely to be the first book a developer picks up.
I was also disappointed to see the introduction of CSS using a
style block in the
head of various examples. The author also mentioned inline styles as an effective way to single out an element for styling. I think more emphasis should have been placed on the benefits of using external style sheets to manage your presentation layer. The author did mention that keeping your style within the same document as your markup is difficult to manage and cause the document to become lengthy and confusing, but it seemed to be mentioned in passing.
As I had said earlier, Sams has an interesting gimmick with their writing style. Separating the chapters into ‘hours’ for easy management can be quite a help to a reader. One recurring pattern throughout the book was constant referral to future chapters. I think to a new reader this would confuse them quite a bit. At some points it seemed as though the future chapters were mentioned just to include a piece of jargon in the text. I assume this is done not only to encourage the reader to continue to the next chapters, it may also be done to conquer any questions the reader might have from possibly hearing these terms before reading the book.
Closing Things Up
@Oliver: That’s a good point indeed. From time to time the book did bring up the various quirks between browsers (mostly the issues with IE), but the examples were pretty basic so coming across anything major wasn’t too common.
Thanks a lot for stopping by!
[…] way, and there are many ways to ensure that your scripts gracefully degrade. There have been entire books written on the subject that offer completely great advice that should be taken into consideration […]