About
The kind of engineer I am
I'm a full-stack engineer, strongest in TypeScript, Node.js and Rust. I care about code outliving me: readable, tested, cheap to run. Rather than a buzzword list, here is everything I've used, with the years attached: skills.
A little bit about me
I'm a developer first. In the past 21 years of JavaScript I've shipped payment platforms, analytics dashboards, a multiplayer poker table, 3D showcases, VR, reverse proxies and middlewares, CLI tools, test frameworks and a domain registrar; most of it on Node.js.
I am passionate about technological advancements, the Unix environment, Git, web stacks, and what I like to call "software philosophy." Over the years, I have gradually shifted focus toward the architectural aspects of my work and team management, but I always return to writing code.
Most of my career was spent in small companies where I owned the whole stack. I also founded Yenom myself. The part I keep coming back to is the build: taking a complicated thing from zero to running, month after month.
How I lead
I've led teams at four scales: I built the India frontend office at AppDirect and trained engineers across the company on QA, Git, Java and JavaScript so everyone worked the same way; I ran releases, architecture and CI/CD for the World Series of Poker game at Playtika as Scrum Master; I led company-wide JavaScript training and code reviews at Morgan Stanley; and I ran the developer-experience program at Stay22 (CI/CD, onboarding, security and feature-flag training).
The short version: I trust people, keep process light, and I'll challenge a decision that isn't working, whether technical or organizational.
The businesses I take over
Some of my work always starts the same way. A company has been on the web since 1999, and the site that got them there is now the thing in the way: a CMS nobody updates, a host that goes down on the days that matter, a form that quietly stopped delivering enquiries months ago, a stack where the one person who understood it left years back. They don't want a redesign pitch. They want it working, and they want it cheap to keep working.
I take those over. I don't show up with a framework I'd rather be using. I learn what they're already on — old PHP, a database nobody can name, pages someone has hand-edited for a decade — and I work inside it first, because a live business can't wait for the rewrite I would have chosen. Then I modernize what's worth keeping, move it off whatever it was about to fall off, and set up the rest so it costs almost nothing.
The bar I hold myself to is deliberately boring: when I'm gone, the site is still up, it costs almost nothing to run, and nobody is on call for it as most of it is automated with self-healing features. My customers buy resilience and stability without surprises, I'm not the hero that they call every time there's an issue because there isn't that much issues.
Adaptability
I work in English and French (native), and can hold a technical conversation in Spanish, Portuguese and German.
The same goes for stacks. I don't ask which framework a company uses before I take the job, and I'd rather be useful in someone else's choice than wait to be handed mine.
I'm drawn to companies that publish what they build. I keep my own machine the way I keep my code: boring, fast, mine to tinker with.
Things I build for fun
The background of this site is my AI training sandbox: arcade games where self-learning neural networks compete, live, in the browser. Four games so far (circuit, cave, highway, climb), plain JavaScript, no ML libraries. I wrote the training from scratch in 2021 and I'm still adding games. Play with it.
There's also Cells AI: a Rust survival simulation of cells that compiles to WebAssembly and runs in the browser. And Ndax Bot, a Rust trading bot with a TUI and hot-reloadable strategies. Yenom started as a side project; it now runs 200+ users on under a dollar a month of infrastructure (Deno + Svelte, OpenAI for the advice column).
When a business need keeps coming back, I extract it into a package and publish it. real-mime-type reads the first bytes of a file instead of trusting the extension; stubborn-server (a Node stub server for mocking, my most-starred repo), css-specs (programmatic CSS tests) and backend-proxy came out the same way.
Personality
Off the keyboard: snowboarding, electronic music, and DJing (Denon SC Live 4, open-source production). I also build audio software for it: dj-viz is a real-time visualizer in Rust, cross-compiled down to a Raspberry Pi.
I also contributed to Epic's open-source Linux shader compatibility for the engine. If you're curious, check out my GitHub profile: the games, the Rust, and the tools are all there.