Mark Hazleton · Wichita, KS
Solutions architect and hands-on application developer. I solve the problem, then get out of the way.
Evaluating my experience? Start with my background
Before anything new gets adopted, I ask whether it produces better outcomes for this problem, this team, right now. Novelty isn't a reason.
Sidetracked by Sizzle: Staying Focused on True ValueI build in response to a need someone can show exists, not one I'm guessing would be interesting.
DevSpark: Change Must Start With a Real NeedI do the work cleanly enough, and document it clearly enough, that anyone competent can carry it on. Solving the problem once means I'm not needed to solve it again.
The Art of Making Yourself Replaceable: A Guide to Career GrowthFrameworks get replaced every few years. Judgment, craft and service are the dependencies I've never upgraded.
The Dependencies I Never UpgradedTwo methods put this into practice: Project Mechanics for managing the work and DevSpark for building the software.
Where 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.”
An ad-free arrow puzzle game, built in a week in a game engine I'd never used.