I've always found this to be a very useful practice. Many projects have a few core files (or packages / modules / whatever) where most of the changes happen. Be

I've always found this to be a very useful practice. Many projects have a few core files (or packages / modules / whatever) where most of the changes happen. Being able to familiarize new contributors (or old returning ones) with those quickly really helps the startup time on a project. I've added architecture files to projects at multiple jobs now [0], [1] and they've been well received. They're not perfect, but they're better than nothing. [0]: https://github.com/zapier/zapier-platform/pull/324 https://github.com/zapier/zapier-platform/pull/324 [1]: https://github.com/stripe/stripe-cli/blob/master/ARCHITECTURE.md https://github.com/stripe/stripe-cli/blob/master/ARCHITECTUR...