Is that an architecture in your pocket?
A lot of developers and architects ask me how they can start learning about architecture. The are usually looking for the “Golden Path” to the one, true architecture for their application. Of course this doesn’t exist. Each system must have it’s own architecture, to support it’s own needs. But, as architects, we do need a mechanism to share what we know, the experience that we build up over our careers. We should be able to say “This is what I built, and this is why it worked in this scenario.” We also need to consider the frames of concern for a model, and discuss those as well. We need to make sure that this knowledge is approachable. There are other industries where they build these giant repositories, and then are ignored. I like to call these ‘ShelfWare’. Others call them ‘Bodies of Knowledge.” More like Dead Bodies of Knowledge. :) No one really uses it, but references it as a bible to defend a bad move or decision. How can we make it approachable? Well, first you can’t req...