I believe software architecture is first and foremost an act of interpretation: designing a system means interpreting a slice of the world and making that interpretation executable.
“Interpretation is Architecture.”
- Software is a medium of meaning — every module, API and event stream encodes how we understand some part of reality.
- Architecture is structured understanding — it makes interpretation explicit, testable and evolvable.
- Systems embody worldviews — choices about boundaries, models, and flows reveal what we take as real and important.
- Design is a stance — abstractions declare what we keep and what we ignore.
- The competitive skill is interpretation — the ability to turn messy reality into coherent, evolving systems of meaning.
Help engineers move from tool-first thinking to interpretation-first thinking — elevating craft from implementation to world-construction, and turning architectural decisions into clearly articulated, governable interpretations.
- Explicit Architecture — making architectural explanations first-class artifacts
- Event-Driven Systems / CQRS / Axon Framework
- Embedded Systems (STM32) — hardware ↔ software integration at the edge
- Cognitive Architecture — how people and systems co-interpret the world
- Philosophy of Software — the epistemic foundations of what we build
- Cognitive Science — how minds structure reality and how systems should align to it
- Event-driven patterns & semantic governance — practical tools for interpretation-first design
- Implementations of Explicit Architecture in production systems
- AI + Embedded systems — bringing interpretation-aware intelligence to the edge
- Reactive / event-driven platforms that preserve semantic clarity
- Tools and processes for semantic governance (Intentional Briefs, domain lexica, change protocols)
Working on “Architecture as Interpretation” — a practical program that turns philosophical concepts (intentionality, distinction, semantic closure, finitude) into engineering artifacts: intent briefs, domain maps, event contracts, and semantic-aware change processes.
- AI can generate code, but it cannot autonomously choose which world to model.
- Frameworks change, but interpretive clarity persists.
- Tools evolve, while interpretation power is the durable advantage. Engineers who can interpret — not just implement — will shape resilient, meaningful systems.
- Core Philosophy: Interpretation-first architecture — make interpretations explicit and governable.
- Practical Focus: Intentional Briefs, bounded contexts as semantic contracts, event streams as narrative traces.
- Research Areas: Software ontology, architectural cognition, time-aware systems, human–AI collaboration in design.
- I treat every system as a worldview — and architecture as the mechanism that makes that worldview actionable.
- I argue engineers are not merely implementers but professional interpreters of domains.
- I’m interested in projects that combine rigorous engineering with explicit semantic governance.
“We do not merely write programs; we make explicit interpretations of the world.”