I think that providing a wide (vs deep) overview of software development is interesting & valuable. It's useful for newcomers, but also for people exploring new

I think that providing a wide (vs deep) overview of software development is interesting & valuable. It's useful for newcomers, but also for people exploring new areas of IT. IMHO it's easier to dive into the details once we have at least a bird's eye view. But I'm a generalist so I'm probably biased ;-) I'm currently writing a series of e-books with a similar goal: https://www.dev-concepts.dev/table-of-contents https://www.dev-concepts.dev/table-of-contents Being aware of ideas, concepts & terms helps a ton to create clear mental models, find solutions more efficiently and reduce tunnel vision (e.g., John Doe works on back-end and thinks that front-end development is simple/easy). Of course a single book, cannot explain all that much, but I really feel like it's possible to share the main ideas, explain the jargon, what matters and why, what to pay attention to, etc. Readers gain a rough understanding of various ideas, and can come back for more if/when they need to dive into other subjects. I'm eager to get opinions/ideas about this.