About
I am a technology and enterprise architecture professional based in Edmonton, Alberta, with more than two decades of experience across software engineering, solution architecture, enterprise architecture, and technology transformation.
Over the course of my career, I have worked with complex systems where technology decisions are rarely just about technology. They involve people, organizations, constraints, competing priorities, risk, governance, and the need to build systems that can evolve.
This site is my personal professional space for documenting what I have learned, what I continue to explore, and how I think about architecture and technology in the real world.
Architecture Notes
Architecture Notes is a collection of practical observations, ideas, patterns, experiments, and lessons from working with technology and organizations.
The notes explore the thinking behind architectural decisions; not simply the technologies used to implement them.
Topics include enterprise architecture, solution and platform architecture, technology strategy, digital transformation, governance, security, systems design, and the relationship between architecture and engineering.
Some notes begin with a practical problem. Others begin with a question, an observation, or an idea worth exploring.
They are written to capture the reasoning, trade-offs, and lessons that emerge when architectural thinking meets real-world constraints.
Thinking About Architecture
I see architecture as a discipline of decision-making under constraints.
Architecture is not simply about producing diagrams, selecting technologies, or defining standards. It is about creating clarity when there are competing priorities, incomplete information, technical constraints, organizational boundaries, and an uncertain future.
Good architecture should provide direction without preventing evolution.
It should help people understand:
- What problem are we solving?
- Why are we making this decision?
- What constraints shape the decision?
- What trade-offs are we accepting?
- How will the system evolve from here?
These questions are at the heart of the ideas I explore through Architecture Notes.
From Experience to Notes
My professional journey has taken me from software development through solution architecture and into enterprise architecture and technology transformation.
Working at different levels of technology has given me an appreciation for both sides of architecture; the strategic decisions that shape an organization and the engineering realities involved in turning those decisions into working systems.
Architecture Notes is where I bring those perspectives together.
It is not intended to be a collection of definitive answers.
It is a record of ongoing learning, professional experience, experimentation, and reflection.