Looking (briefly) at the TOC for the book it is not clear if there is a sections on best practices, debugging, code organiztion etc. Lately I have been using JSLint for improving code and would like to know what else people use.
The book is concerned with code quality insofar as it attempts to provide a best-practice approach for every task it tackles, and highlights related decisions in the explanation page.
JSLint is certainly a good tool to use (particularly bound to Command+S in TextMate ;-)) as it promotes good habits, although some of them are not about code design or code quality per se, but more about making sure your code minifies well :-)
In general, the quality principles for JS are much the same as for other languages: clarity (e.g. meaningful identifiers, pertinent use of comments…), conciseness (which is not just brevity, but brevity without losing readability; 5 readable lines running adequately fast are better than half a line running at lightspeed but being unfathomable), modularity, etc.
Another source I follow is the google group - JSMentors.
Joined: Jan 28, 2008
JSMentors is pretty good, and the intent and guidelines for it are commendable. Good resource!