Reviews for JSP, a practical method of program design

The average rating for JSP, a practical method of program design based on 2 reviews is 3 stars.

Review # 1 was written on 2013-06-24 00:00:00 E James Douglas ugh. This book was suggested by the reddit popular "How to learn javascript properly" program as a good way for total noobs to learn javascript. This book is horrible for learning how to program. It is an excellent Javascript reference book, but it's not something to just sit down and read straight through. I can barely get through a few pages at a time without my brain feeling fried. It goes into the minutiae of every aspect of the language but rarely ever explains why anyone should care or any practical way that the detail matters.

Review # 2 was written on 2020-12-01 00:00:00 Cwengile Gagela Of the JavaScript books I've looked at, this is the one I would recommend to any and all people getting started with the language. On the plus side, it is comprehensive, systematic, clear, and generally well-written. I am amazed how often even classic books on programming languages are stuffed with basic errors, such as presupposing information they have not yet explained, not commenting code samples, or introducing multiple concepts at the same time. This volume is free of such errors. On the negative side, it is systematic and consistent to a fault, always working methodically from basic concepts up to higher-level ideas. This is a good fit with its comprehensive scope, but it comes at a significant cost. Pedagogically speaking, the best way to introduce a new idea is usually to give practical examples and to walk through them. In some chapters, it takes many pages to get to the first concrete illustration of any practical code - in particular, I think of the crucial and very long chapter on client programming. I found that the author's uniform adherence to a systematic exposition often made ideas more difficult to assimilate, and I sometimes had to put the book down and go to other tutorials for an introduction to ideas that immediately answered my key questions. In my view, all technical documentation whatsoever should begin by answering the questions "What is it?" and "What does it do?" Despite its liabilities, which make it in some ways more useful as a reference than a practical introduction, as I said I would recommend this book to literally any programmer getting started with JavaScript. Its virtues are considerable, and I have no doubt I will return to it again and again.