Librarian Note: There is more than one author in the Goodreads database with this name. This profile may contain books from multiple authors of this name.
This book is a good starter to deep in node development.
First 3 chapters do a good job introducing the reader into the environment. The premier is reduced to only one chapter yet enough to get the essentials of JS and TS to continue with the main topic of the book; Node.js. Although I personally believe the first chapter could be an introduction or a preface rather than a chapter per se.
From here I recommend having the Node.js documentation (and maybe the JS’ if you’ve missed or didn’t get something in the premier). Concurrency and streams aren’t an easy cookie so you’ll struggle a bit because of the abstractions Node does.
Unit testing was one of my favourites chapters (after the premier). The author shares his experience and teaches testing in a short and concise manner. Even though I believe there’s room to include more examples you could read a more specialised book in this matter.
After that tough passage we’re ready to start diving into more web-dev stuff. And the book does a great job showing the potential of pure Node and also some third-party libraries. The thing I liked the most at this point is that until now the author has used a code style similar to mine. Trying to get everything in their place and taking advantage of modules as much as possible. This makes the code examples (and projects) cleaner, therefore easier to follow.
And finally we get to the capstone of the book (IMO). The big project “Sports Store”. Even though I’m not a big fan of splitting the project in many chapters I believe the author made the right call here. Since the project evolves to the point we prepare it to be deployed in a production environment using containers. Of course there’re many ways to do that depending on your actual project.
Things I didn’t like: - Summary tables at the beginning of the chapters may be confusing or even can give the reader the notion that they already know enough.
- This might be subjective. I believe the author shouldn’t take that big shot trying to stuff a lot of things in a unique book. I think the author could’ve omitted the premier part (even though it was a good chapter) to include more details in the node.js stuff. That he includes references (some links are broken BTW) but could have been included as a summary at least. For example the event loop Node uses; the phases to be more concrete.
Things I did like: - Good code samples. Clean and right to the point. Highlighting the important stuff. - The project is one that gives the reader a sense of working in a real-world project. I mean this in a way that the author makes the project grow progressively
- Not sure if the author intended this book to be beginner friendly. But this books is beginner friendly enough to get you ready to start developing web apps. The rest comes from here comes from experience.