Open to difficult, useful problems

Give me the messy system. I’ll find the useful path through it.

I’m a systems-oriented software engineer working across Python, Linux, containers, application security, applied AI, desktop software, and game systems.

current
Open-source maintainer & security work
default loop
spike → iterate → stabilize
build bias
Python for glue C for guts
Illustrated tired operator holding an orange coffee mug at a computer
operator.state calm under ambiguity
coffee nominal

Core Maintainer

Security Manager

Applied AI Builder

Indie Game Developer

01 / Selected evidence

Claims should leave fingerprints.

Filter the work by the kind of problem you care about. Turn on evidence mode for the ownership and engineering signal behind each project.

02
Private engineering tool Python / Podman / Git

Review Ops

Resumable review tooling that pins Git ranges, hashes artifacts, treats candidate instructions as hostile data, and confines required execution to secretless, offline probe containers.

Owned signal: evidence-bound findings, bounded subprocesses, stale/duplicate guards, immutable probe inputs, and human-controlled publication.

trust boundariesreview systems
Private / described at system level
03
Cross-platform desktop PySide6 / audio / AI

DJ Blue AI

Mood-aware meeting assistance, audio playback, transcript capture, and Gemini-powered chat with persistent configuration, component previews, smoke tests, and tag-triggered releases.

Owned signal: brought UI, playback, transcription, configuration, packaging, documentation, and Linux/macOS/Windows release paths into one operable desktop product.

desktopapplied AIrelease
04
ML platform PyTorch / RunPod / Vast

Chess Bot

An end-to-end platform for dataset validation, PyTorch training, top-k and legality evaluation, inference, local play, and cloud GPU lifecycle orchestration, with a standalone Streamlit arena for playing against swappable model artifacts.

Owned signal: connected data generation, training, evaluation, inference, UI, cloud execution, tests, committed behavior specifications, and a separate CPU demo deployment with draggable-board play.

PyTorchpipelinescloud GPUarena
05
Local-first agents LangGraph / Qdrant / RAG

Local Agent Tools

Tool calling, conditional routing, streaming, checkpoints, Qdrant-backed retrieval, local llama.cpp models, safe knowledge-base operations, and deterministic research flows.

Owned signal: explored agent orchestration as an explicit state machine with local models and controlled tool boundaries rather than a chat wrapper.

agentsRAGlocal LLM
View source
06
Small native product C / SDL2 / CMake

Clean Mines

A compact Minesweeper implementation for desktop and terminal with a native C core, self-tests, CMake builds, and cross-platform release automation.

Owned signal: evidence that the “C for guts” part is real: deliberately small scope, explicit memory/runtime boundaries, and portable builds.

CSDL2portable
View source
07
Playable game Godot / simulation / releases

Code Review Simulator

A strange idea taken through the entire loop: review pull requests from a physical apartment, cash out, buy upgrades, automate the work, and live with what the automation gets wrong.

Owned signal: gameplay systems, diegetic UI, performance work, cross-platform builds, release automation, screenshots, public devlogs, and a playable browser build.

01game systemsshipping
Play / view devlog

02 / Operating model

Fast first pass. Durable final state.

The speed comes from reducing uncertainty early, not by pretending it does not exist. Pick a phase to inspect the loop.

question / 01

What is actually unknown?

Map the system and trust boundaries. Reproduce the risky behavior. Build the smallest probe that can disprove the convenient story.

  • System map before architecture theatre
  • One thin end-to-end path
  • Evidence captured beside the claim

03 / Review instinct

I review the invariant, not just the diff.

High-risk changes rarely fail only where the patch is loudest. I trace the intended behavior through code, persistence, authorization, execution boundaries, and regression coverage.

Read the ATS-friendly version
  1. 01
    Reconstruct

    State the intended invariant and ownership boundary.

  2. 02
    Trace

    Follow code, state, permissions, persistence, and tests.

  3. 03
    Reproduce

    Separate the PR regression from an existing defect.

  4. 04
    Probe

    Test the smallest safe fix in an isolated lane.

Beyond the headline

The same builder, different surfaces.

A Debian host, a local speech-to-text tool, an ML experiment pipeline, a native desktop app, and a Godot prototype all ask the same question: can someone understand, operate, and continue this after the exciting first pass?

Lab bench

Low-level curiosity, honestly scoped.

Digital logic, a working 4-bit CPU and custom assembly-like instruction set in Turing Complete, plus IC10 automation. Useful proof of curiosity; not presented as professional processor design.

04 / Contact

Bring a problem with edges.

Systems engineering, maintainer tooling, security-sensitive application work, applied AI, or an odd prototype that deserves to become real.

quick.nav

Where do you want to go?

Tip: press Ctrl + K from anywhere.