Software developer · Lifeplus

I build the boring parts properly.

Production software at Lifeplus, systems work in Unity, and short write-ups on what actually broke.

Selected work

Lifeplus
2026

Auditing a data-integrity bug across production history

Problem

A per-transaction flag had been written incorrectly by an earlier bug. Nobody knew how many historical records were wrong, and a blind mass-update across a live production table was not an acceptable way to find out.

Built

An audit that recomputes the correct value for every record and reports disagreements without writing anything, then repairs only what the fix is responsible for — with a threshold that aborts the run if the disagreement count comes back higher than expected.

Outcome

Scanned hundreds of thousands of production records in about two seconds. Production came back clean, making the repair a verified no-op. A pre-production environment was repaired. A third tripped the abort threshold and was deliberately left alone for investigation rather than mass-written.

SQL · T-SQL · TypeScript · Database migrations

Lifeplus
2026

A regression suite where every test was proven capable of failing

Problem

A test that passes proves nothing on its own — a check that can never fail looks identical to one that works. On a system where a wrong result means mis-shipped goods, a green suite was being trusted without anyone establishing it would go red for the right reasons.

Built

Coverage across unit, integration, full-API and browser-driven levels, with a standing practice: for every new test, deliberately reintroduce the bug it guards and record that it goes red, plus a control proving it does not fire on a legitimate look-alike.

Outcome

Over a hundred test files and a full-API harness at roughly eleven thousand lines. One change’s records covered fourteen injected faults, each confirmed to turn its test red. It caught real gaps: an over-broad string match passed its own test while silently hijacking an unrelated case, found only because the control used verbatim production text rather than an invented one.

TypeScript · Vitest · Playwright · Docker · SQL · CI

Personal
Ongoing

Game lab — Unity systems

Problem

Production work is bounded by what the business needs. I wanted something with no brief attached, where the architecture decisions were mine and the only deadline was my own.

Built

A Unity URP world demo: procedural terrain, biome data assets driving placement and presentation through a registry, editor tooling for authoring them, plus combat, squads, save/load and scene setup.

Outcome

Two phases shipped across four months, a third in progress. The biome system replaced hardcoded placement logic with data assets, which is the same instinct as the work above — put the rules somewhere you can inspect them.

Unity URP · C# · Editor tooling

Roadmap and detail →

Field notes

About

I write production software at Lifeplus — features, internal tooling and workflow support on a real team, shipping into a system where a wrong result means goods go to the wrong place.

Before that I studied Computer Science and Data Science at Lyon College, and spent seven years repairing appliances. That second one turns out to matter more than it sounds: diagnosis under uncertainty, and the discipline not to trust your first theory.

Contact

Open to talking about software, data work, or systems problems.

click to reveal email · Résumé (PDF)