Slash dotted

Woot – the book, The PHP Anthology: 101 Essential Tips, Tricks & Hacks, 2nd Edition, has been slash-dotted – and they actually liked it giving it a 9/10 rating. *gasp*

The reviewer, Michael J. Ross, seems to only have 5 major grips with the book overall:

  1. Firstly, a reader hoping for a well-edited book will likely become distrustful by the authors’ misuse of the term “that” in place of “who.”
  2. Secondly, there are far too many ambiguous comments in the first-person, e.g., “I would dare to say that…” In a book written by five authors, the reader naturally has no idea who is speaking.
  3. Thirdly, there is a fair amount of inconsistency in the formatting of the code throughout the book, including indentation and other spacing, as well as variable naming.
  4. Also, every instance of a “{” on its own line (presumably to line up vertically with the corresponding “}”), is an antiquated waste of space, since any decent programmer’s editor or integrated development environment (IDE) can do brace matching automatically.
  5. Lastly, almost all of the section titles begin with the phrase “How do I.” That is fine within the body of the book, at the beginning of every section. But when dozens of these section titles are listed together in the table of contents, that phrase could be excised so each section’s topic would be faster to spot, and there would be fewer unnecessary words.

I can live with those, (to me they are kinda minor),though I have to admit to being the person with a “{” on a new line – sorry but I like my code formatted that way when I am left to my own devices. Call it a quirk if you will – I like to see my braces visually line up.

On the plus side he remarks:

The chapters on error handling and access control are alone worth the price of the book.

Since I was responsible for the chapter on access control – I will take that as a pat on the back.