Mark Hazleton · Wichita, KS
Solutions Architect/Developer. Project Mechanics is how I manage the work; DevSpark is how I build the software.
Career chapters, current role and the outcomes behind them.
How I decide what to keep, what to replace and how to move without losing the business.
A consolidation exampleWorking Sparks, from the tools I use every week to experiments made in public.
Essays on AI-assisted delivery, architecture and how software really gets built.
Leadership essaysProject Mechanics is how I manage the work. DevSpark is how I build the software. They're separated by decades of technology change and connected by one concern: keeping intent attached to delivery.
Methodology
How I manage the work
How is the engagement structured so people, decisions, accountability and outcomes stay aligned?
Explore Project MechanicsSince 2026
How I build the software
How is the software built so intent stays connected to architecture, code, tests, knowledge and production behavior?
Explore DevSparkWhere I think out loud about architecture, AI and what building software actually teaches you.
The Sparks that carry the most weight and what came of them. The full stories, including the problem and the decisions, are on the Work page.
A tool I use several times a week. One package reference and one line of code give any .NET 10 API its own interactive test harness.
The way I build software now. It runs in most of my active repositories, including this site.
The HTTP plumbing my own projects run on, with thousands of NuGet downloads.
A brand-new local business that customers could find and call from day one.
“Above and beyond anything I could have ever dreamt of.”