did you read it on your own? Or as a part of a uni course? It it a classic, sure, but it's definitely not a book to recommend to beginners. Many compiler engineers and academics think the book is... Outdated a bit.
It felt quite outdated to me. I tried reading it quite a few years ago as a student, but gave up on the books old-fashioned ideas.
The book is very imperative and doesn't really know much about modern abstractions for data structures.
Something like https://en.wikibooks.org/wiki/Write_Yourself_a_Scheme_in_48_... is probably more fun for a beginner these days. (Languages in the ML family are really well suited to writing parsers, interpreters and compilers. That what that family of languages was designed for.)
Well, these 2 books lie on the academic side of language implementation / compilation. Both outstanding, but I cannot really suggest these to working programmers.
A very easy way in would be a venerable Wirth's "Compiler Contruction", which takes a simplistic approach, e.g. concentrating on getting the result out as fast as possible.
Somewhat similar, crisp in style and exposition, would be Nystrom's "Crafting Interpreters". It explains modern interpreter kind of language implementation (Python, JS, PHP and others), which includes compiling to bytecode and bytecode VM. There is a free online version of the book.
Now, compilers are one of the oldest area of computer-related software research. There are many good books, numerous approaches and schools. Any recommendation should take concrete student's background into account. Say, improving a massive modern compiler backend requires a very different kind of recommendation compared with a make-my-own-language project.
While it was commonly used, it really isn't that good of a book.
Would you believe it doesn't discuss looping structures at all? No repeat, while, for loops.
Last time I looked, for the latest edition of the book, you had to create a timed online account to access the chapters they didn't include in the book anymore. Ridiculous. Use any other book, I'd say.
I think you can say that all insurance have at least partial network effect built in. Quality of underwriting comes from a diverse and large risk portfolio, which leads to profits and pricing accuracy.
Locksmith use to do the same kinds of scam on 411 services and yellow pages listings. The fees to have multiple business phone lines with the phone company was the real curation.
You can also have a convoy of 1 manned truck with n driverless truck that play follow the leader. You end up with a train model on the road infrastructure.
Once I heard Marissa Mayer recount that she asked Sergey Brin where he got the idea of doing such a minimalist design for Google. Sergey's answer was: I don't do HTML.
There's similar quotes in an interview with Larry and Sergey in "Designing Interactions" by Bill Moggridge. Sergey explains (in a lot more detail than I do here) that they kept the front page simple because they didn't want to spend too much time on the front page. Only afterwards did they realise how powerful that was, and they decided to keep things off there as much as possible.
