see ya space cowboy...
I build tools for understanding, testing, and improving complex software systems.
My work sits around developer tooling, build systems, program analysis, and AI coding agents. I like problems where useful structure is present but hard to see: repository history, build graphs, code search, verification, system boundaries, and agent behavior. I build small research instruments and practical tools to make that structure executable, measurable, and easier to reason about, then write about what I find.
I'm especially interested in small, technically ambitious teams working on developer tools, build systems, code intelligence, AI infrastructure, evaluation, or research-heavy software. I do my best work when the problem is still a little strange and the right abstraction has not been decided yet.
Typical themes: opaque software and infrastructure, security boundaries, developer tooling, and AI-agent workflows — made easier to inspect, debug, and trust.
Small, bounded work tends to fit best: diagnostics, internal tools, repo or CI cleanup, observability hooks, eval or reporting passes, dashboards, or documentation that makes a system legible.
Developer tools & build systems. Fast feedback loops, build graphs, reproducible environments, CI, code search, repository interfaces, and tooling that makes large software systems easier for humans and agents to operate.
AI systems & verification. Coding agents, eval harnesses, deterministic supervision, repository-specific behavior, and systems for turning model output into evidence you can actually inspect and trust.
Research engineering. I like taking an odd technical question, building the smallest instrument that can answer it, running the experiment, and following the result even when it kills the original hypothesis.
I'm primarily looking for a full-time engineering role, but I'm also open to unusually interesting focused projects.
If you are not sure how to scope something, describe the system and what feels unclear — we can pick a narrow first slice.
My Background.
Search through my back catalog.
I adopted Buck2 for code generation. It gradually ate remote execution, experiment tracking, and workflow orchestration.
Turning accepted code edits into executable hypotheses, freezing them, and testing whether they can reproduce changes developers make in the future.
Comparing structured retrieval, Bash, and graph-guided search policies with SearchBench.
I build tools for understanding, testing, and improving complex software systems.
My work sits around developer tooling, build systems, program analysis, and AI coding agents. I like problems where useful structure is present but hard to see: repository history, build graphs, code search, verification, system boundaries, and agent behavior. I build small research instruments and practical tools to make that structure executable, measurable, and easier to reason about, then write about what I find.
I'm especially interested in small, technically ambitious teams working on developer tools, build systems, code intelligence, AI infrastructure, evaluation, or research-heavy software. I do my best work when the problem is still a little strange and the right abstraction has not been decided yet.
Typical themes: opaque software and infrastructure, security boundaries, developer tooling, and AI-agent workflows — made easier to inspect, debug, and trust.
Small, bounded work tends to fit best: diagnostics, internal tools, repo or CI cleanup, observability hooks, eval or reporting passes, dashboards, or documentation that makes a system legible.
Developer tools & build systems. Fast feedback loops, build graphs, reproducible environments, CI, code search, repository interfaces, and tooling that makes large software systems easier for humans and agents to operate.
AI systems & verification. Coding agents, eval harnesses, deterministic supervision, repository-specific behavior, and systems for turning model output into evidence you can actually inspect and trust.
Research engineering. I like taking an odd technical question, building the smallest instrument that can answer it, running the experiment, and following the result even when it kills the original hypothesis.
I'm primarily looking for a full-time engineering role, but I'm also open to unusually interesting focused projects.
If you are not sure how to scope something, describe the system and what feels unclear — we can pick a narrow first slice.
see ya space cowboy...
My Background.
Search through my back catalog.
I adopted Buck2 for code generation. It gradually ate remote execution, experiment tracking, and workflow orchestration.
Turning accepted code edits into executable hypotheses, freezing them, and testing whether they can reproduce changes developers make in the future.
Comparing structured retrieval, Bash, and graph-guided search policies with SearchBench.