Thanks for the suggestions @bottlenecked.
at the start of each chapter/section a little summary of what the goal of the chapter is and how we’re going to go about it. I feel like I’m blindingly following the instructions
I think this is great feedback. I don’t want the book to feel that way.
essentially making a plan and executing it goes somewhat against the TDD style this book looks to impart
I don’t think having a master plan goes against BDD/TDD. In fact, I think not considering design or approach is a misunderstanding of TDD for a lot of people. We can’t completely check out brains at the door and follow errors. We have to consider the design.
When I go through each chapter, I have a master plan in my head, but I imagine I’m just not communicating it enough. So, I think your original feedback is very helpful.
One question I had, how detailed a plan are you thinking of? I have something in my head when we talk about a master plan, but I wonder if its the same thing you’re thinking.
If you have a sense of what kind of master plan would be helpful, let me know. And thanks again for the feedback.
