The Architecture of Open Source Applications

Favorites: - SQLAlchemy by Michael Bayer: https://www.aosabook.org/en/sqlalchemy.html (nice observation of core language on top of SQL, then the separate declarative/orm system) - LLVM by Chris Lattner: https://www.aosabook.org/en/llvm.html - Audacity by James Crook: https://www.aosabook.org/en/audacity.html (interesting mentionings of wxwigets) Note that pretty much everything in volume 1 and 2 is interesting, though! What would be nice to see, non-exhaustive: - Blender: Especially 2.80, an analysis of its…

I've had the idea for a while to start a club to read through open source projects, compile them, extend them, note architectures and design decisions, look at documentation and CI/testing organization, etc. Do something like one project per month with one topic among the above per week. Haven't found the right group of folks to experiment on with this yet. Edit: Send me an email if you'd like and I'll think about hosting this virtually.

"Architects look at thousands of buildings during their training, and study critiques of those buildings written by masters. In contrast, most software developers only ever get to know a handful of large programs well — usually programs they wrote themselves — and never study the great programs of history. As a result, they repeat one another’s mistakes rather than building on one another’s successes. This book’s goal is to change that." Excellent point.

Hmm. I get the sentiment (500, i.e. not too short, not too long), but 500 lines will mean different things for different people and different programming stacks. It literally can mean 50000 vs 500 "lines of knowledge" required. I'm not sure why would you name your book like that. Consider: 500 lines of defensively written web server C++ code. 500 lines of C driver code. 500 lines of assembly. 500 lines of php script. 500 lines of java server app…