It seems like a daunting task to take on so much, so props for the work put into this. It does kind of read like a beta, with the exception of the bigger thre

It seems like a daunting task to take on so much, so props for the work put into this. It does kind of read like a beta, with the exception of the bigger thread (which makes it feel a bit more like an alpha). If that's okay, I'd like to offer my thoughts on this. What I'm reading from the chapters and the first few pages (dense in information!), is that there are initial assumptions and an over-arching structure that would benefit from being highlighted. The undocumented assumptions are about both the audience and your own approach: Where are your target readers at, who are they in broad terms? What prerequisites are necessary for this book to be manageable, and since it covers multiple fields it's possible to offer some insights into other sources (whether online or physical books or classes) that offer fundamentals, up to perhaps even a parallel to what you're putting together. The unannounced structure seems (as of right now) to be: (1) Notes about stuff (2) We're dealing with humans (3) We're dealing with humans in a system (4) Related and/or other relevant systems (5) What do we do as an engineer in this mess? (6-7-8) How does that practically unravel ? (9-10) Here's a crash course in mathematical stuff we'll need later (11) Regression. A lot of it. (12) Some other stuff than Regression to think about too (13-14) Practical applications of the last 4 chapters we've been going through (15) Let's introduce R now! I think it would read better if there was some progression along those lines: (1) Tells you what this book is at its core, then very briefly what's going to hit you, and which assumptions you will make and what prereqs your readers might need/rely on (1-bis) Marked optional: Historical stuff, contextual stuff not directly related to the book's core but useful nonetheless. Perhaps the reader will want to take a look at that at their own leisure. (2) Bring in the practical tool you have a preference for (R), since it's both useful for data manipulation/visualization and programming concepts. Nothing big, the learning can and will happen throughout the book. Now you can leverage that tool to illustrate (and low-key practice) the concepts that you introduce about various fields. The next few chapters don't need to change too much but they can be made much more interactive by using R, jupyter notebooks, etc. (3) Who do we build stuff for? (Humans) (4) Humans don't live in a vacuum, so let's consider their system (5) (Perhaps marked optional) Those systems coexist and interact with other systems. Why it's relevant to know about a few. (6) What do we do as an engineer? (Build, design, creatively, etc) (7) Basically your 6-7-8 with some fun R stuff --- And I'd honestly end there, and separate the rest into its own book. That book can be about introducing the maths, with more or less optional parts/prereqs, leveraging R, introducing the bits of data manipulation that are deemed useful, and so on.