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 full-stack at Montpellier Engineering — React/Next in the morning, PHP frozen for ten years in the afternoon, and a bit of Tauri / mobile when the need leaves the browser.
Evenings and weekends, it's gamedev (HELLBOUND, Phaser 4) and low-level (firmware C, Vulkan exploration). Secondary to the day job, but it shapes how I think about code: perf, data, memory.
What keeps me in: 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.
The craft. Modern UI, type-safe, no fluff. And legacy PHP when needed, because prod doesn't wait.
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.
Anthropic SDK direct, never LangChain. Multi-provider when cost or routing calls for it.
My practice ground. Strict strategy pattern, polish & juice non-negotiable.
When the mission goes to the metal: firmware, data scripts, Python glue.
The invisible 50% that keeps a project from drifting.
Short timeline, the essentials. From the first PacMan to satellite firmware.
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.
−87% on inference cost, measured on my own SaaS. Dynamic routing to the cheapest capable model — OpenAI direct, no wrapper.
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".
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 SaaS (CvGen LLM selection).
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.
FULL-STACK DEVELOPER · WORK-STUDY → CDD
Full-stack web development across several industrial client projects: web, field IoT, internal desktop tools. Front React 19 / Vite 7 / Tailwind 4 / shadcn/ui, back in-house PHP + MariaDB, desktop Tauri 2 + Ed25519 auto-update. Alongside: defensive cybersecurity audit (EBIOS RM) delivered to management, GitLab/LDAP config, WCAG AA-driven design system.
▸ 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.