Software Development
In the previous post, we introduced the idea of the 4E framework and discussed the first two of the “E”. In this post, we will discuss the remaining two “E” and complete the ideas of the framework.
In the previous post, we concluded the discussion of the Why, the purpose of architectural work, by looking at the cognitive and the humane facets of architectural work. We also briefly discussed that AI agents are not able to satisfy these traits of architectural work unless you solve solved problems time and again.
In the previous post, we discussed the economic purpose of architecture. The economic purpose is probably the most emphasized facet regarding the Why of architectural work, yet hardest to grasp in its entirety and the hardest to get right. However, this does not mean that the other facets would be of less importance. But as they do not immediately emphasize time and money, they are often pushed aside in our highly commercial…
In the previous post, we discussed several architectural anti-patterns. We have seen that we are a lot more vulnerable to them if we do not understand why we do architectural work, i.e., understand its purpose. We understood that the focus and thus value of architectural work is accidental without having a clear understanding of why we are doing it.
In the previous post, we started discussing that not understanding why we do architectural work leads to many detrimental anti-patterns in software development. We can observe these patterns time and again: