No, and this also can be slightly confusing, because the same term, "design", is used to refer to two completely different things: the process used to develop the visual and user-facing part of a web application or website (which is web design), and the activities preceding the technical implementation of the application (web application design, which is actually a specialisation of software design).
The term "web development" applies to the development of both websites and web applications. The topic of this book is web application development.
Yes, most definitely. In fact, if you're a beginner, then you're in luck as you haven't had the chance to build up bad habits. You can anticipate a long — albeit interesting — ride!
If you're a non-web programmer or developer, then you obviously have an advantage when it comes to actually writing code and transitioning to a new programming languages, and perhaps you're already acquainted with practices such as behaviour-driven development and DevOps that are highly useful when working on web development projects, but there's still a long list of web-specific skills you'll need to pick up.
If you've already tried your hand at web development and recognise yourself in the vignettes depicted in the introductory section of the home page, then the typical bottom-up approach to self-taught web development isn't working for you, and you'll certainly find that the top-down approach taken by this book is instrumental in taking your web development to the next level — and in removing the experience of frustration in the process.
Rather than focusing on the syntax of programming languages and features of frameworks, Web Development in Real Life covers the full application development lifecycle in a top-down approach, from the idea to operations to ongoing maintenance and evolution, and gives you the knowledge you need to become proficient and efficient.
The examples that are given are based on popular tools and implementations, but their main purpose is to illustrate the topic under discussion, not to teach you the syntax (the references section of the book provides suggested reading for that).
This actually depends on your background: if you're an expert web developer then you probably already have a deep understanding of the topics covered in Web Development in Real Life and you just need to know how they're implemented in X or Y, so indeed go ahead and get a book on X or Y. In other cases you need to nail the concepts first. Once you get to the chapters on programming you should start reading some material on X or Y (offline and online reading suggestions are included in the references section of the book) to a) learn the syntax, features and gotchas of X or Y, and b) work on the exercises included in the book to practice what you've learnt.