Crafting Interpreters <a href="https://www.craftinginterpreters.com/contents.html" rel="nofollow">https://www.craftinginterpreters.com/contents.html</a><p>Writing an Interpreter in Go <a href="https://amzn.to/2PA5LEh" rel="nofollow">https://amzn.to/2PA5LEh</a><p>Let's Build a Compiler <a href="https://compilers.iecc.com/crenshaw/" rel="nofollow">https://compilers.iecc.com/crenshaw/</a><p>Awesome list of compiler resources <a href="https://github.com/aalhour/awesome-compilers" rel="nofollow">https://github.com/aalhour/awesome-compilers</a>
I cut my teeth on the "Dragon Book", but as you say once you get past the syntax analysis material it becomes increasingly opaque. Most books are written to be used as part of some CS curriculum. Only a tiny number of SEs go on to work on compilers.<p>Personally I found the Nanopass approach much easier to understand because it breaks down the compilation process into lots of simple transformation steps: <a href="https://nanopass.org/" rel="nofollow">https://nanopass.org/</a>