I am a Staff Software Engineer rooted in hands-on software engineering. I work at multiple levels of the system, from code and runtime behavior through business and organizational boundaries. I work with and across teams of individual contributors to make difficult systems clearer, safer to change, and more useful to the business.
My work combines legacy modernization, production reliability, distributed observability, system cartography, and carefully bounded AI-assisted tooling.
- Website and portfolio
- Targeted Principal Software Engineer resume
- Career timeline
- Architecture case studies
- Advisory and consulting engagements
- Writing and field notes
- Modernize legacy systems with explicit seams, observability, and reversible migration steps.
- Map static code, runtime behavior, historical evidence, and organizational ownership into one working system model.
- Build internal technical communities with durable communication channels, delegated ownership, mentoring relays, and clear handoffs.
- Apply OpenTelemetry and service-level objectives to understand normal system behavior before changing it.
- Build local-first and bounded AI workflows with human review, provenance, deterministic checks, and no assumption that model output is authority.
Phalanx Duel is a real-time tactical game and architecture laboratory. It explores deterministic simulation, server-authoritative state, replayable action logs, WebSockets, and human-led AI-assisted engineering.
The site preserves a growing oral history of software communities, technical conferences, and engineering practice across the Midwest and beyond.
- UGtastic and WHOIS Tech Community archive
- Video and transcript archive
- Interactive career and technology timeline
- SCMC archive
- Archive methodology
Canonical identity maintenance is coordinated by Zarathustra and the
canonical-surface-steward skill. The Hierophant, Fool, Commissar, and
Watercourse personas handle canon, contradiction checks, process, and minimal
change.
The archive distinguishes organic writing, source-backed transcripts, and AI-assisted syntheses. AI may help preserve, search, or organize the record. The public interpretation remains human-led and carries the relevant provenance and uncertainty.
This Jekyll repository contains the public site, canonical resume data, archive metadata, deterministic query tools, and validation workflows.
./bin/pipeline build
./bin/pipeline ci
ruby bin/audit_public_surface.rb --strict
ruby bin/query_career_datalake.rb --helpRun ./bin/pipeline ci locally before committing generated changes. GitHub
Actions uses ./bin/pipeline verify to build, test, and validate the
committed artifacts without regenerating them.
Install the local fail-fast hooks once with ./bin/install-git-hooks. The
pre-commit hook runs the fast checks. The pre-push hook also verifies generated
artifact freshness before a branch reaches GitHub.
Local archive roots and corpus databases belong in ignored local configuration. They are never required for the public site build.
- Contributing
- Public artifact curation policy
- AI content disclosure and provenance
- Public surface audit
- Changelog
Please report security issues privately through SECURITY.md. Do not open a public issue containing credentials, private personal information, local filesystem paths, or unpublished archive material.
The repository is a public archive. Contributions should use public-safe, source-supported material and should not add secrets, environment files, private corpus exports, or machine-specific paths.