Production Troubleshooting Methodology

Production issues are among the most demanding challenges a software team can face — especially when they occur in environments outside your direct control.

To navigate these situations effectively, this methodology draws inspiration from the OODA loop (Observe, Orient, Decide, Act), a strategic decision-making framework originally developed for military operations. The goal is to establish control, gather facts, and make deliberate progress toward resolution — even in the face of complex or obscure problems.

Continue reading

OO Design is more about ‘Doing’ than ‘Being’

One of the most profound insights I have learnt about OO is that class design — the shaping of classes & types — is best informed by what processing needs to do, rather than the ‘kind’ of entities it goes between.

What we are talking about here is behavior, rather than trying to categorize entities at rest. Program code only acts by being executed; classes & interfaces (types) are a mechanism to despatch that execution to specific methods.

This shows that OO is really about active behavior, rather than any other arbitrary notions of classification.

But shouldn’t inheritance just follow Entity Properties?

At this point, we’ll address a common interjection — what about bean-style entities, and their properties? Surely inheritance should just follow these! Continue reading