- Cyb3rSyn Labs - Newsletter, Library & Community
- Posts
- Residuality: A Paradigm Shift (Part 2)
Recently, I had the incredible opportunity to sit down with with Barry O'Reilly and chat about his work on Residuality theory and his call for a paradigm shift in software architecture.
In Part 1, we discussed his journey in questioning mainstream software architecture and his path toward formulating Residuality Theory, driven by observing patterns in successful architectures that emerged from stressed models rather than fixed requirements.
This newsletter brings Part 2 of that conversation. In this exclusive episode, Barry explains how his approach to architecture fundamentally differs from traditional risk management within the engineering paradigm.
He posits that focusing on predicting known risks makes systems fragile, while his method uses random simulation of potential system states to train architecture for criticality, the ability to survive unexpected conditions.
O'Reilly also discusses the philosophical underpinnings of software engineering, arguing that the ingrained logical and engineering mindset can hinder the adoption of new paradigms like residuality, which acknowledges inherent uncertainty and the limits of models.
He also provides an excellent parting advice for budding technologists that differs from conventional “networking” advice or career strategies.
“As to methods there may be a million and then some, but principles are few. The man who grasps principles can successfully select his own methods. The man who tries methods, ignoring principles, is sure to have trouble.”
Reply