You may wonder why my publication rate in this blog has decreased dramatically. I am staying at home due to an infection for three weeks now which wasn’t that helpful for my blog.
To keep things running I have decided to create a new posting. Well, the title is intentionally related to my current health situation.
To be honest, I think that software architecture design reveals some interesting commonalities with sickness:
- Both often require intense treatment by experts
- Different experts offer different opinions and treatment plans
- Both are typically open-ended to some extent
- Both are not subject to planning in most situations
- Both mostly feel very miserable
- To reduce the risk of getting infected some kind of prevention strategy is always a good advise
- It is better to cure the cause not the symptoms. Thus, be aware of all interdependencies and follow a holistic approach
- Viruses are a problem in both worlds
- Healthcare never ends – it is important in the whole lifecyle
- Learning from failure is recommended to avoid similar problems in the future
- Prevention is always better (i.e, cheaper) than healing
Most software architectures I know are not in a good and healthy shape - at least in some intermediate phases. Why? Because they were not devleoped with the aforementioned bullet list in mind. Thus, health monitoring (i.e, reviews) and treatments (i.e., refactoring) should be an essential tool in the architect’s framework.
Does this sound reasonable?