This seems a lot like evaluating an article about OS kernel design based on whether it covers Mach-style message IPC and zerocopy TCP performance. From experience teaching developers how to use things like yacc, it's hard to pick up without the concepts.

Also, bristling a little bit at the comment that you need parser generators for anything but "toy" languages; read Hanson's LCC book for a design, implementation, and justification of a hand-coded recursive descent parser. Without having written a hand-coded parser, you might also fall into the trap of thinking you need an "RD-parser" tool to build one.

Finally, this article covers code generation, something most people totally skip. "So mid-90's" --- yeah, well that attitude may explain why we're still evaluating ASTs and bytecode arrays in our most popular languages.

I loved this series.