Comment by crewindream
13 hours ago
Good architecture reduces cost, while still achieving business goals.
(E.g. If you have problems hiring for a weird stack, it increases hiring cost; you have problems with dependency zoo maintenance it increases costs; if it took a year to build a framework that could've been a bash script, it increased the cost)
Every other architecture “metric” should be useful/convenient proxy towards reducing overall cost.
I completely agree but cost conversations are difficult to have in most orgs especially when some of the costs are hard to measure (e.g. hiring, future time investments etc.). The goal of every (commercial anyways) software is to deliver maximum value at minimum cost.