About / Perspective / Practice
Technology has been the constant.
Curiosity keeps it moving.
My work has moved through computer engineering, cybersecurity, technical customer advisory, PreSales, Consulting and Leadership. The common thread is a fascination with what happens when complex technology has to work in the real world.
I have always liked the point where technology stops being abstract.
Architecture diagrams, security controls and emerging technologies are interesting on their own. They become much more interesting when a customer, a team or an organization has to make them work under real constraints.
That is why my professional world has rarely stayed inside one technical discipline. Cybersecurity naturally leads into identity, devices, applications, data, architecture and operations. Technical customer work adds priorities, stakeholders, budgets and decision processes. Leadership adds another system entirely: people, focus, communication and the conditions in which good work happens.
The useful part of technical depth is not knowing more details. It is knowing which details matter to the decision in front of you.
01 / Journey
Different roles.
One recurring problem.
How do you preserve technical truth while making complexity understandable and actionable?
A foundation in systems thinking: hardware, software, interfaces and the discipline of understanding how the pieces actually connect.
Technology under adversarial conditions — where assumptions, permissions and edge cases matter because someone may deliberately exploit them.
Complex requirements, architecture, demonstrations and proof of concepts — translating capabilities into decisions and measurable outcomes.
Building repeatable approaches, developing teams and exploring how AI changes workflows, decisions and the design of technical organizations.
02 / Principles
How I like
to work.
Not rules for every situation. More like defaults that have proven useful across technical, customer and leadership work.
Understand before prescribing.
Solutions become much better when the real constraint is clear before the technology enters the conversation.
Make trade-offs visible.
Security, usability, speed, autonomy and control are rarely binary choices. Good decisions need the trade-offs in the open.
Prototype before institutionalizing.
A small realistic experiment often produces better information than a large plan built around untested assumptions.
Keep technical depth connected to value.
The goal is not to simplify technology until it becomes vague. It is to explain enough of the right detail to support a better decision.
Prefer systems over isolated tools.
Applications, identities, people, data and processes interact. Optimizing one component without the relationships usually creates surprises elsewhere.
Leave room to change your mind.
A strong point of view should survive evidence — and change when the evidence is better than the assumption.