Software Architecture Principles

The key is to break things down to as many small projects as possible, and ideally have 1 person working on each, parallelization is key.

Modules are always black boxes, you dont care what the module does. You talk to it through its interface, API, protocol, whatever. You never must have to look at that code, it just works, and you just use it through its very easy and helpful for-human documentation.

Some modules are for senior people, some modules are for junior people. As long as the API interface is fucking good, you can write shit, rewrite shit, change everything without it breaking anything. Thats amazing.

You already knew this though.