Networked multiplayer, distributed computer vision across 32 machines, and now interactive games for live streams — the same problem every time: keep state in sync, keep latency low, keep it running while people are watching.
Shipped things, not concepts. Each one is running somewhere right now.
Viewers type 1 or 2 to pick a side; every gift adds a dancer to their line. Two halay lines, arms linked, pulling a rope — the score moves the knot, the losing line gets dragged in. Runs as an OBS browser source at 1080×1920, driven by a local event bridge that reads TikTok's LIVE socket with no login and no signing service.
Dixon-Coles rating model with xG blending, priced against the bookmaker's market, with de-vigging, fractional Kelly staking and a graded prediction record. Syncs 1,400+ fixtures and prices from iddaa's bulletin feed every 20 minutes.
A complete otome visual novel: seven story scripts, twelve endings, synthesised score, generated art pipeline, and an Android build — written, scored and illustrated end to end.
A computer-vision automation system scaled across 32 concurrent machines: a hybrid C++/UDP client talking to a Python/TCP server, with low-latency telemetry, feedback loops and automated response logic.
An idle hero RPG for portrait mobile: deterministic stat simulation, balance sweeps, a headless test suite, and a screenshot harness that renders the real UI without a display.
A viewer-controlled tug of war dressed as a wedding halay. Two lines of dancers, arms genuinely linked, the leader waving a handkerchief. Every gift adds a dancer and pulls the rope; the knot drifts toward whoever is winning and the losing line visibly leans in.
Contract work and product builds. C#/C++ when it matters, Python when it pays, web when it ships.
I take on a small number of builds at a time. If it involves real-time state, a stream, a camera or a deadline, tell me what you're trying to do.