Clean Architecture: A Craftsman's Guide to Software Structure and Design (Robert C. Martin Series)

Notice how well those three align with the three big concerns of architecture: function, separation of components, and data management.

If you give me a program that works perfectly but is impossible to change, then it won’t work when the requirements change, and I won’t be able to make it work. Therefore the program will become useless.
• If you give me a program that does not work but is easy to change, then I can make it work, and keep it working as requirements change. Therefore the program will remain continually useful.

architecture is to minimize the human resources required to build and maintain the required system.

The goal of software architec

we’d wanted the behavior of machines to be hard to change, we would have called it hardware.

The only way to go fast, is to go well.

These developers buy into a familiar lie: “We can clean it up later

These developers buy into a familiar lie: “We can clean it up later

goal of software architecture is to minimize the human resources required to build and maintain the required system.

low-level details and the high-level structure are all part of the same whole.