Doby Baxter Computing

When your systems fail, they should fail loudly and tell you exactly why

Validation layers, observable AI pipelines, and forensic tooling for teams that can’t afford silent failures.

If your team loses hours to configuration that breaks in production, LLM workflows that fail without warning, or incidents no one can fully explain — I turn that fragility into systems that are predictable, observable, and hard to misconfigure.

Fewer production surprises Invalid states are caught at definition time — before they ever run.
Failures you can trace Observable pipelines and evidence-backed reconstruction, never guesswork.
Config teams can trust Schema-driven validation that turns fragile YAML/JSON into a safety net.

Proven in production, not just promised

Solve this for my team → See the work Start a conversation

< Professional Endorsement />

"Doby has demonstrated strong technical skills, thoughtful system-level thinking, and a clear focus on usability and maintainability. He played a key role in developing innovative tooling driven by real user and community needs. He is proactive, reliable, and communicates clearly, particularly when working on complex or cross-cutting features."
– Mission Payload Senior Software Engineer, European Space Agency

< What I Do />

Focused engineering around one idea: systems that are predictable, observable, and hard to misconfigure.

Configuration & Validation

Schema-driven layers that catch bad config before it runs.

AI Workflow Reliability

Deterministic, observable LLM pipelines that don't silently break.

Developer Tooling

CLIs and internal tools that reduce friction for engineers.

Scientific Software

Python tooling & configuration systems for simulation and research.

Security & Forensics Tooling

Evidence-traceable incident reconstruction that never guesses.

Systems Architecture

Building maintainable software foundations that scale with teams, products, and research.

See all services & licensing →

< Let's build something reliable />

Integration support, contract engineering, scientific software, or open-source collaboration — tell me what you're working on. I usually reply within 3–5 business days.

Get in touch → About me
Micro navigation assistant
Ask Micro for help