[oriel]

This reminds me of the (relatively) recent post about breakdowns and descriptions of major and well-crafted applications.

Link: http://aosabook.org/en/index.html

A lot of Computer Science graduates, and/or self-taunt engineers are missing the commentary of 'masters' or senior people who can say why and why not this or that way.

Just like the difference between building a bridge across a river and in your backyard is far more than just scaling up, seeing design patterns and common pitfalls writ large is one more step towards proper education needed for a modern programmer IMO.