Software architecture requires balance. During the 20 years I’ve been leading technology organizations to build products, mostly via Agile, I’ve learned some rules that have helped me — and my teams — successfully strike the right balance. These aren’t technically focused rules; they’re more generic, so they apply to monolithic, layered, service-oriented, and microservice architectures equally well. One of these rules is the subject of this Advisor.
Advisor
![Chaos Is Constant, So Continuously Refactor](/sites/default/files/styles/square_thumbnail_180x180_/public/BEA/2019/Advisors/bea190703_1.jpg?itok=0duuHpWj)
Don’t have a login?
Make one! It’s free and gives you access to all Cutter research.