Writing

Software architecture is the clinical process of choosing which specific set of problems to manage rather than searching for a perfect solution. This approach prioritizes clear boundaries and system legibility to ensure that the internal structure remains a maintainable asset instead of a technical liability.

Shifting the accessibility narrative from a compliance chore to a high-level engineering constraint, exploring how color blindness and screen reader logic force better information architecture.

We’ve inherited the "handover" from the world of physical manufacturing. In that world, a blueprint is finalised, signed off, and sent to a factory floor where the variables are controlled and the outcome is static. But software is not a toaster; it is a living system of state, fluctuating data, and unpredictable human behavior.