Technical notebook / lab
I work as a full-stack developer and product engineer with a strong DevOps bias, designing, shipping, and operating Angular applications, mobile products, backend systems, and developer tooling that have to survive real production constraints.
Proof
Each snapshot below is attached to a concrete product or delivery context, not dropped in as an isolated vanity metric.
Bibliocards combines 14k MAU, a catalog of 150k photocards, and more than 15GB of media under a stack I build and operate myself.
It is the strongest proof on the site because it validates product ownership, app delivery, backend design, storage decisions, and routine production responsibility in one place.
A store operations platform used by 100+ stores in France, with low churn and growing adoption, across kiosk interfaces, web surfaces, cloud functions, and analytics cost management.
The signal here is not just scale. It is sustained work on a system that had to stay usable, evolvable, and economically reasonable over time.
A healthcare-professional data platform for Brittany replacing a buggy proprietary tool, with 15GB of operational data and a frontend delivered solo inside a small cross-functional team.
This matters because it shows delivery in a more constrained environment: legacy replacement, operational reliability, and coordination across frontend, backend, CI, and infrastructure automation.
Selected work
A solo-built K-pop photocard platform combining catalog depth, recurring revenue, and full-stack operational ownership.
Solo product engineer across mobile, backend, database, deployment, and operations.
An Angular integration package for Better Auth, created to reduce framework friction and improve developer experience.
Package author, maintainer, API designer, and documentation writer.
Critical healthcare data tooling in Brittany and a retail SaaS used by more than one hundred stores, delivered across frontend, backend, infra, and operational cleanup.
Angular, Spring Boot, Firebase, BigQuery, GitHub Actions, Ansible, Capacitor, and long-lived product constraints.
Featured case study
A solo-built K-pop photocard platform combining catalog depth, recurring revenue, and full-stack operational ownership.
Solo product engineer across mobile, backend, database, deployment, and operations.
Bibliocards is the anchor project because it combines product traction, recurring revenue, a large catalog, mobile delivery, backend services, and ongoing operational ownership inside one system.
Why it matters
Experience
Rebuilt a critical healthcare-professional data tool for Brittany after a costly proprietary solution became unstable and hard to use.
Frontend lead in practice, with support on backend, CI/CD, infrastructure automation, and team workflow.
Helped evolve a store operations platform used across France, moving it from paper-based tracking to a multi-surface digital workflow.
Full-stack product engineer across kiosk app, web app, cloud functions, data costs, and architectural cleanup.
Writing
Rebooting the site on a lean Astro and MDX setup before rebuilding the full portfolio.
A field note on keeping a retail SaaS data stack useful while staying disciplined on analytics and infrastructure cost.
Notes on turning manual server setup into something safer, reproducible, and easier to reuse across client work.
About
I work comfortably across app surfaces, APIs, infrastructure, and delivery mechanics. That range matters because the most interesting systems rarely stop at one layer. The portfolio is intentionally built around full-stack, product, and DevOps-oriented engineering work rather than generic showcase pieces.