COEF — first pilot-phase review
Five restaurants signed up, one in daily use. 55 invoices validated, 482 lines read by the AI: a photo, Claude extracts, the owner validates. And 382 tests that block deployment on the slightest failure.
I build AI-powered products end to end — and I co-founded one: Coef, in production since July 2026. The AI has a precise job there: reading restaurant owners' invoices, without the token bill spiraling. From React / Next down to embedded C / C++, I go wherever the product needs me.
Technical co-founder of Coef. Master's-level, expert in secure software development: what I ship to production, I also know how to defend.
Four dossiers. Coef, which I co-founded, shows what I do best: shipping AI that serves the product, without burning the budget. Security, embedded and mobile round out the picture; the rest lives in the archive.
Operational logbook — what plays out under the hood, written short, while it's fresh.
Five restaurants signed up, one in daily use. 55 invoices validated, 482 lines read by the AI: a photo, Claude extracts, the owner validates. And 382 tests that block deployment on the slightest failure.
Cycle counter always armed, an on-screen measurement strip, the GPU's share of the drawing. Only then the gains: vector text tessellated when large, rasterized when small, fixed decoration in a few objects instead of forty.
Coef starts with a restaurant-owner partner. He handles the field and sales; I handle the product and all the tech. Same day: first commit, and first restaurant created in the database.
PUS-C compliant TM frame, CRC-16 encoding, mirror parser on the ground side. The firmware fits in 3 KB of stack, zero malloc. The moment the CCSDS doc becomes readable.
Enemy behaviors (idle / patrol / chase / search) split one file per state. The 400-line switch had become unmanageable. Simpler to reason about, test, and extend.
The site read too generic. Pivot to a committed operator-briefing direction: MGS phosphor palette, Anton for display, Departure Mono for HUD. Codec easter egg as a bonus.
Full audit of a critical web stack. Flow mapping, threat scenarios, reduction measures. Deliverable: a detailed report and prioritized remediation plan, landed on an executive desk.
PWA dashboard for technicians under full sun. 7:1 contrast, 56 px touch targets, offline mode. UX proven in the field, with gloves on — not in a meeting room.
When an AI provider drops at 2am, the cloud router fails over to the next one without a break. Anthropic SDK direct, never LangChain: less magic, more control.
First structured position. Legacy PHP / MariaDB on one side, early-adopter React 19 / Tailwind 4 on the other. Navigating two eras of code in the same day.
A project, a scoped mission, an architecture question, or the urge to talk C?
All welcome. Reply within 48h, by me, not a bot.