DAILYMOTION STUDIO — CANDIDATE PREMIERE · ONE NIGHT ONLY
Seven years shipping to production. The last two entirely in React 18 & TypeScript 5, on the kind of product Studio is: a data-heavy dashboard where non-technical users pilot a complex system — sensor fleets then, video libraries tomorrow.
Every good feature needs a conflict. Here's mine — as written.
INT. LEGACY FRONTEND — MONDAY MORNING
A 445-line chart component glows on the screen. Fetching, rendering and business logic tangled together. moment-timezone imported straight into the views. Documentation: sparse. Tests on this layer: none.
YOHANN (calmly, opening a new folder called core/)
“We isolate the domain first. React stays at the edges.”
MONTAGE — THE REBUILD
Bounded contexts appear: Comfort, Energy, Metrology. Ports & adapters draw a hard line between domain and infrastructure — HTTP, dates, storage, all injected. Use-cases arrive test-first, with success and failing stubs. Even time itself gets an interface: IDateProvider, deterministic in tests.
THE CODEBASE (six months later)
“Views are thin presenters. Effects are declarative listeners. The year view renders instantly — the server aggregates, the client stays calm.”
SMASH CUT TO: PRODUCTION — STILL RUNNING
The product shipped continuously through the whole rebuild. No big-bang rewrite. No broken releases. Just a codebase the next engineer can finally build on.
— exactly the “explore unfamiliar codebases, turn messy problems into clean solutions” your posting asks for. This isn't a metaphor; it's a repository.
Why this story ends at Dailymotion.
I've spent two years making complex data legible for non-technical people — thresholds, filters, exports, i18n, multi-tenant theming. Creator dashboards are the same craft with better content.
React, TypeScript, REST — daily tools. GraphQL is my honest gap: the hard parts (fetching, caching, normalizing client state) are already my job; the query language is a short bridge I'm actively crossing.
Startup and product-company background, comfortable in ambiguity, allergic to micromanagement. I write specs before code and share updates before you ask.
I use Claude Code fluently and review every generated line like a colleague's PR. These two candidacy sites are the live demo — AI-built, human-directed, fact-checked.
Hover to pause. Everything listed has shipped.
CAST — IN ORDER OF APPEARANCE
C & SHELLÉcole 42, 2016
JAVASCRIPT / JAVADawan, 2019–21
DJANGO · CELERY · REDISOOTI · Papernest, 2021–23
REACT 18 · TYPESCRIPT 5Accenta, 2023–25
FASTAPI · LLM · MCPiDem Agency, 2025–26
FRONTEND
STATERedux Toolkit · listener middleware
DATAVIZRecharts · Chart.js · adaptive rendering
STYLEstyled-components · SCSS · CSS Modules
TESTSJest · React Testing Library · TDD
BUILDWebpack 5 · GitLab CI/CD
SUPPORTING
APISREST/DRF veteran · GraphQL bridging
BACKEND LITERACYPython · Django · FastAPI · PostgreSQL · MongoDB
AI TOOLSClaude Code, reviewed line by line
LANGUAGESFrench (native) · English (C1)
PRODUCTION
WRITTEN & DIRECTED BYYohann Lesueur
BUILT WITHClaude Code (Fable 5) — how → /guide
NO FACTS WERE HARMEDin the making of this candidacy
POST-CREDITS SCENE
The sequel is called “Yohann at Dailymotion Studio” and it's in pre-production. Green-light it with one email — I'll come with honest answers, strong dashboard opinions, and my keyboard.
github.com/yoles · linkedin.com/in/yohann-lesueur · prefer the product cut? open the Studio version