Operator profile: background, stack, ground rules. Kept honest, updated when things move. If a technology isn't listed here, I either haven't practiced it — or I'd rather master it before I claim it.
First real project in June 2023: a vanilla PacMan. Today I'm a developer at Montpellier Engineering — React / Next, legacy PHP when prod demands it, and more and more embedded C / C++: touchscreens on STM32, Qt 6 HMIs.
Since July 2026, I'm also the technical co-founder of Coef, a SaaS for independent restaurant owners. I own all of the product and all of the tech; my partner owns the field and sales. That's where I learned that steering a project is mostly deciding what not to do.
The rest of the time: gamedev (HELLBOUND, Phaser 4) and space firmware (Apogee). What keeps me in, everywhere: projects where you have to learn something. If I already know how to do all of it, it's probably too small.
// disclaimer: I don't claim to master everything. What I know well is marked as such. The rest, I say so.
Sorted by axis and tier. PRIMARY = my daily work. SECONDARY = solid, used regularly at work or on the side. ALSO = I can use it, without making it my core.
AI serves the product, not the other way round. Anthropic SDK direct, cost measured, fallback when a provider drops.
The craft. Modern UI, type-safe, no fluff. And legacy PHP when needed, because prod doesn't wait.
Co-founder of Coef: from scoping to production, and the trade-offs in between. Saying no is part of the job.
When the product is a screen, not a browser. Measure before optimizing, allocate before running.
Field and consumer apps. When a PWA no longer cuts it, I go native without flinching.
Internal tools outside the browser. Ed25519-signed auto-update, clean distribution.
My practice ground. Strict strategy pattern, polish & juice non-negotiable.
Scripts, glue, small APIs. Useful, not my core.
The invisible 50% that keeps a project from drifting.
Short timeline, the essentials. From the first PacMan to a startup in production.
My first real lines. Ugly, wobbly — but it moved on screen, and I never stopped after that.
Ethereum and smart contracts. Where I really understood the cost of gas.
Started work-study. Front React, back PHP, desktop Tauri run in parallel.
Design system built for work gloves: big buttons, hard contrast, offline mode.
Full-stack continuity — React/PHP/Tauri on the industrial portfolio.
Necromancer survivor. Strategy pattern everywhere, polish takes as long as the gameplay.
CCSDS/PUS-C telemetry stack. The first real "I don't know yet, I'm learning by building".
SaaS for restaurant owners, with a restaurant-owner partner. First commit and first restaurant on July 9; in production at coef.tech.
The day job goes down to the metal: embedded GPU, PC simulator, C++ widgets. Same rule as everywhere: measure before optimizing.
My own rules. Not universal — just kept, because they've saved me two or three times.
No god-class with a 400-line switch. From gamedev (HELLBOUND × 3 axes) to firmware (Apogee, isolatable modules).
A feature with no visual or audio feedback is a bug with a name. Hit pause, screen shake, particles, audio.
Never LangChain. Less black magic, more control. When a prompt goes off the rails, I know why in five minutes.
Next 16, React 19, Tailwind 4, Phaser 4, Tauri 2.10 — on the stable release, never before. No experimental in prod.
Project code is 50%. The rest: shared tooling, monitoring, design systems, mocks, docs.
No overclaiming. Vulkan, I touch it without mastering it: so it stays personal. Apogee, I'm learning it by building — and that's stated in black and white.
At Coef, the AI has a precise job: read invoices and advise. The rest is plain, tested code. Saying no to AI is part of the work.
DEVELOPER · WORK-STUDY → CDD
Full-stack web and embedded development across several industrial client projects: web, field IoT, desktop tools, touchscreens. Front React 19 / Vite 7 / Tailwind 4 / shadcn/ui, back in-house PHP + MariaDB, desktop Tauri 2 + Ed25519 auto-update, embedded C on STM32 and C++ / Qt 6 HMIs. Alongside: defensive cybersecurity audit (EBIOS RM) delivered to management, GitLab/LDAP config, WCAG AA-driven design system.
TECHNICAL CO-FOUNDER
Food-cost tracking SaaS for independent restaurant owners, at coef.tech. I wrote 100% of the code and I'm the software's publisher: design, interface, AI (Claude API), POS integration, hosting, security, GDPR, e-invoicing, support. Pricing, priorities and positioning are decided together.
▸ END OF DOSSIER
You read this far. Either the profile genuinely interests you, or you're procrastinating. Either way, the rest is on the other side.