Hi Kevlin, hi Trisha, I've browsed the table of contents and it seems the topics are distributed randomly through the book. How you recommend to read the book: cover to cover or is there an recommended order by related topics?
The articles are in alphabetical order by title. Since there's no over-arching narrative, that seemed as good an approach as any!
With two of the other 97 Things books (Programmer and Architect), I read them cover to cover, skimming where appropriate. I'd recommend either that approach, or taking a look at the contents and picking out the ones that interest you most first, then going over the others in order.
How you recommend reading the book: cover to cover or is there a recommended order by related topics?
years before I had the same dilemma whenever I pick up a new Technically heavy book , the method I choose to do it and it
worked well for me as a voracious reader over the years is to first read a couple of chapters to get the broader idea important
to read the "Preface " or Introduction , Prologues"then jumping to the topics which interests you
Few people choose to read to cover to cover , so choose what works best for you.
It is difficult to fit a simple flow to the many diverse topics, so we chose the order that would be fairest and also the easiest to refer back to. I did this with 97 Things Every Programmer Should Know and we did the same for 97 Things Every Java Programmer Should Know. Because the topics are so short, the range and diversity of subject matter you can cover in one sitting has a rounded completeness to it!