About Me

Staff Software Engineer focused on platform reliability, architecture, and making complex production systems safe to change.

How I Work With Teams

I work at the seams of software systems: between code and runtime behavior, across distributed services, and between engineering squads and business goals. Having guided platforms through multiple technology shifts and modernization cycles, I focus on helping teams make difficult systems safe to change:

  • Meeting teams where they are: Production systems are shaped by real business constraints and shifting deadlines. I don't bring dogma or judgment to legacy code; I look at what the software actually does in production and help find the next safe improvement.
  • Clear, written architecture: I write explicit Architecture Decision Records (ADRs), system cartography maps, and visual diagrams so teams share the same picture and never rely on guesswork.
  • Collaborative pairing and mentorship: I enjoy working directly with engineers, untangling difficult transactional paths together, and building lasting confidence within the squad.
  • Pragmatic simplicity: I prefer simple, standard-library approaches over speculative abstractions. The best architecture is usually the simplest one that solves the real operational problem.

What I Value on an Engineering Team

Software engineering is a shared discipline played over long horizons. Technical decisions matter, but how teams treat each other while doing the work matters even more:

  • Curiosity over blame: When an outage or defect occurs, we investigate the systemic causes, improve the guardrails, and update our telemetry. Blameless post-mortems build resilient systems and confident teams.
  • Fast feedback loops: Deterministic automated tests, fast local builds, and observable runtime traces build developer velocity. When verification is fast and trustworthy, deployments become routine.
  • Generosity with context: Siloed knowledge creates bottlenecks and anxiety. Great engineering cultures are built on pairing, written documentation, and celebrating team growth.
  • Room to ask naive questions: Great engineering teams make it safe to question assumptions, admit when something is unclear, and run small experiments. When people are not defensive about legacy code, complexity gets resolved faster.

Background & Lineage

My technical background spans early distributed commerce, real-time networking, enterprise platform modernization, and community stewardship:

  • Production Systems: Built and operated high-volume transactional services, from early real-time ticket broker inventory locking to 10-year enterprise monolith cartography and zero-downtime database migrations.
  • Community & Mentorship: Co-founded Software Craftsmanship McHenry County, helped organize regional developer gatherings, and founded Geekfest@OMF and the OpenTelemetry Working Group to support continuous peer learning in large engineering organizations.
  • The Oral History Archive: Founded UGtastic (preserved on this site as the WHOIS Tech Community archive), recording 218 in-depth conversations with software pioneers and working practitioners across fifteen years of the software craftsmanship movement.

About This Site

The domain just3ws.com was registered on October 4, 2000, representing over 26 years of continuous, unbroken ownership. Coined at the dawn of the web era as an affectionate reference to the World Wide Web ("just three 'W's changed the world"), it serves as my self-hosted digital home, root namespace, and canonical anchor for all independent engineering, writing, and archival work.

This site serves as my professional home and as a permanent, durable archive for software community history. Every conversation, transcript, and case study is backed by stable IDs and structured data so these records remain accessible for years to come.

If you are navigating a platform transition or want to explore an engineering collaboration, feel free to get in touch or review my full resume.