I'm a curious technologist who likes working where product engineering, cloud operations, solution engineering, documentation, and user experience all collide.
My favorite work is turning messy signals into practical decisions: what is ready, what is risky, what needs to wait, and what evidence actually supports the call.
I care about work that makes complicated things easier to reason about. A passing test should create confidence. Documentation should reduce uncertainty. Process should help people move faster because the important risks are visible.
I am especially interested in:
- Readiness, risk, and decision systems
- Test automation strategy for workflow-heavy products
- Feature flag ownership, rollout, and retirement practices
- Documentation quality, docs drift, and technical content architecture
- Accessibility, user empathy, and the human side of software delivery
- Developer community, conference organizing, and shared learning
- Building the Release Quality Toolkit as a public home for practical team artifacts
- Drafting practical resources around docs audits and quality signals
- Co-organizing developer and DevOps community spaces in Kansas City
- Writing about testing, accessibility, engineering empathy, and the human systems behind software
- Thinking a lot about how teams decide when they know enough to ship
Life Updates
2026: Building a more intentional public GitHub presence around technical curiosity, useful systems, documentation, and community work.
Now: Turning scattered frameworks, checklists, and hard-won lessons into reusable public artifacts.
Show Writing
I write about testing, accessibility, empathy in engineering, community, and the sometimes-weird human systems behind software delivery.
Show The Thread
| Thread | What Pulls Me In |
|---|---|
| Quality | Test strategy, confidence, risk analysis, useful signals |
| Delivery | Readiness, decision support, learning loops, stakeholder communication |
| Automation | Workflow coverage, useful reporting, signal quality, maintainability |
| Feature flags | Scope, ownership, defaults, test paths, controlled rollout, retirement |
| Documentation | Audits, content structure, stale-content detection, user-centered explanation |
| Community | Meetups, conferences, talks, facilitation, welcoming technical spaces |
Show Projects
A public collection of reusable checklists, decision templates, visual guides, and readiness artifacts for teams that want better shared confidence.
Topics include release readiness gates, feature flag inventory, go/no-go decision support, post-release review structure, and test suite configuration patterns.
A practical framework for auditing stale technical documentation, scoring documentation currency, prioritizing remediation, and keeping docs aligned with the product users actually see.
Status: starter repo drafted locally.
An evolving space for thinking about test evidence, automation reports, and the gap between "tests passed" and "we know enough to ship."
Status: starter repo drafted locally.
Show Community Work
| Contribution | Community |
|---|---|
| Co-organizer | DevOpsDays KC |
| Co-organizer and host | DevOps KC Meetup |
| Organizing team | Kansas City Developer Conference |
| Co-host | BrowserStack Local Meetups |
Show Working Principles
- Competence over credentials
- Execution over rhetoric
- Signal over noise
- Substance over polish
- Clear scope boundaries
- Useful automation
- Teams that are honest about what they know and what they are guessing
I like making complicated things easier to reason about.