About
I’m a technical leader and hands-on architect with a long background in web platforms, content management systems, and full-stack software development. I’ve spent much of my career working in the space between architecture, delivery, and the day-to-day reality of building software with teams.
What I do
My core work is software architecture, platform development, technical leadership, and practical problem-solving. I’ve worked deeply with Drupal and web-based content systems, along with React, Node.js, PHP, Python, JavaScript/TypeScript, GraphQL, SQL, and infrastructure tools like AWS, Azure, Docker, and DDEV.
I’ve built and supported software across public safety, healthcare, benefits administration, asset management, public sector platforms, startups, and mission-driven organizations. The domains change, but the underlying work is often similar: understand the problem, make the system easier to reason about, and help the team move with more confidence.
I like rapid prototyping and deeper systems thinking because it gets ideas out of abstraction. I draw from Design Science Research, Human-Centered Design, and tools like the Phoenix Checklist because they give structure to the thinking and building process.
How I work
I try to stay close to the actual work. Strategy matters, but it becomes more useful when it is connected to code, architecture, delivery habits, and the people who have to maintain the system after the first version is released.
I’m comfortable moving between different levels of detail. Some days that means writing code or reviewing implementation details. Other days it means helping a team think through a roadmap, a migration, a content model, a delivery process, or a technical decision that needs to be shaped and framed clearly.
I value calm communication, steady progress, and shared ownership. I believe good teams are built through trust, clear thinking, useful feedback, and a habit of improving the work.
The best projects, for me, are the ones where the work becomes clearer as it moves. The team understands the system better. The tradeoffs are easier to name. The next decision is less mysterious than the last one.
Ideas I return to
These are a few ideas I come back to often. They show up in how I think about work, teams, software, and the long process of getting better at my craft.
-
Don’t worry, be happy.
Meher Baba -
We are what we repeatedly do. Excellence, then, is not an act, but a habit.
Aristotle -
Everything should be made as simple as possible, but no simpler.
Albert Einstein -
It is not the answer that enlightens, but the question.
Eugene Ionesco -
The future is already here, it’s just not very evenly distributed.
William Gibson
Resume archive
I keep older resume versions here as a small archive. They show how my work has changed over time, from development roles into architecture, leadership, platform strategy, and more recently applied AI and advisory work.