3 ms·
Your marketing pitch is excellent and hit right at how I would have described my pain point with my knowledge of React 4 months ago. It still speaks to me and I
by afarrell 11y ago
Your marketing pitch is excellent and hit right at how I would have described my pain point with my knowledge of React 4 months ago. It still speaks to me and I feel an urge to give you money.
I have one problem though:
Why do you only introduce unit tests in part 12 out of 13? When I "Imagine how quickly I can get all of your work done with the right tools and best practices", it involves me being able to write solid automated tests for everything. Not only that, but if you introduce the proper way to set up testing early and carry it through the rest of the book, it helps the student keep themselves on track. When they get stuck, having a failing test helps them focus and have a clearer idea of how to move forward.
I strenuously urge you to introduce testing earlier.
- jashmenn 11y agoYes, this is great feedback and we'll definitely introduce testing, to some degree, earlier than chapter 12. That chapter will be an in-depth guide to unit testing React generally, but we'll introduce testing some of the example code in other chapters earlier in the book.
- afarrell 11y agoI think the ideal would be introducing testing toward the beginning (perhaps after you give them the initial basic mental model) so that someone has a recommendation for the testing library they should use which will work for the rest of the book. Then, every so often when you notice that something is hard to test, have a sidebar to help them along. This does kinda eliminate having a chapter on it though, unless you have something how to migrate from legacy frontend code to react/redux (which actually would be pretty valuable, though it sounds like a tall order to me).