With my Dev Concepts collection (12 books I'm writing), I'm taking a different approach. Instead of saying "developers absolutely have to know/do this" (which i

With my Dev Concepts collection (12 books I'm writing), I'm taking a different approach. Instead of saying "developers absolutely have to know/do this" (which is often biased/opinionated/situational), I'm just explaining all the ideas/concepts/principles I can think of. That way, curious developers can explore and learn about things they didn't know existed (and might benefit from knowing or applying to their own context), or need to learn about to solve an issue they're facing. It will take me quite a while to get where I want to be with this project, but I'm confident that a good chunk will be timeless; even if there are many moving parts in IT, there's a huge amount of pretty stable ideas/concepts. Sorry (not sorry :p) for the shameless plug, but here's the link: https://dev-concepts.dev https://dev-concepts.dev. I'd be thrilled to exchange ideas about this!