Felipe Cardini Full-stack engineer.

For the last three years I've been part of the team building and fixing TRACE, the carbon measurement platform behind thousands of events. Node, MongoDB, React, and I design what I build.

cardini.dev

Served by Felipe · London

22 Nov 2026

What this page cost to load, itemised
1 × HTML 27.8 KB
1 × Styles 21.5 KB
3 × JavaScript 3.7 KB
1 × Font (name only) 2.5 KB
1 × Icon 0.3 KB
0 × Images 0.0 KB
Subtotal 55.8 KB
Compression discount −37.9 KB
Total sent 17.9 KB
CO₂ this visit 0.003 g
Measured on every build.
Thanks for visiting!

Work · Oct 2023 – present isla / TRACE

TRACE lets event organisers measure, reduce and report their events' Scope 1–3 emissions, using carbon data aligned with the GHG Protocol. I'm part of the engineering team that builds and runs it, working closely with our senior lead.

About TRACE · About isla

Cut infrastructure costs by retiring Redis

Problem
Edit-locking (which stops two users overwriting the same data) depended on a separate Redis instance we were paying for.
Decision
Re-implemented locking in MongoDB, which we already ran: a lock document marks a table as being edited, and a TTL index expires it automatically so a lock can never get stuck.
Result
Removed the Redis dependency and its monthly cost, with no change for users.

Shipped a feature a year before its backend existed

Problem
A dashboard module needed company-wide data that required a long backend refactor.
Decision
Built an interim, frontend-only solution with the aggregation logic in the client, so users got the feature straight away.
Result
It ran bug-free for ~12 months until the backend refactor landed.

Built a public API for a client's own dashboard

Problem
A client wanted to enter data in TRACE but see the results in their own custom dashboard.
Decision
Designed a token-based auth system and request middleware, and exposed the data through a public API.
Result
TRACE data now feeds the client's dashboard directly.

Also at isla

  • Took over a codebase built by outsourced agencies: refactored, fixed bugs and consolidated duplicated logic across the platform.
  • Replaced Product Fruits, a paid onboarding tool, with an in-house guided-tour system built on a React tour library, cutting another subscription.
  • Designed and built an internal stats site in Retool for senior staff, pulling live data from our database.
  • Set up PostHog for product analytics and monitoring.
  • Stepped in as the product’s designer during the phases we had no designer: user flows, UI and assets in Figma.

Side business MAGDRY: a product I designed, built and run

A patent-pending magnetic gym towel, sold on Amazon UK. I built the brand site in plain HTML and vanilla JavaScript, no framework, with AI assistance (video hero, conversion-focused layout, deep-linked Amazon checkout), and I run the business side: listings, advertising and product development.

Visit magdry.co.uk

Projects Things I've built

Braincloud

Live word-cloud app for presentations: the audience submits words anonymously and the most popular grow in real time, with an admin area for session logins.

WebSockets · MongoDB Atlas · React

Charla

Private chat rooms in seconds: no sign-up, nothing stored, conversations disappear when the browser closes. While they chat, people can play a custom tic-tac-toe I built, with every move synced live between players over WebSockets.

WebSockets · React

Process How I work with AI

Most of my code now starts with an AI draft. I write roughly 20% by hand; the rest of my time goes into specifying the problem, reviewing what comes back, and testing it. I treat AI-written code like any other pull request: nothing gets merged until it’s been reviewed.

The mistakes I catch are rarely syntax. More often it’s a confident fix built on a wrong assumption, because the model hasn’t seen enough of the codebase, or logic that’s more complicated than the problem needs, with names that don’t say what things do. So I control what context it gets, ask for the simplest version first, and rewrite and rename before anything merges.

About Always building for the web

Building for the web has been the constant in everything I’ve done. For four years I ran my own pizzeria business, and alongside the operations I designed, built and maintained its website and ran its marketing. That’s where I got hooked on building things, so I trained formally through Northcoders and made software my full-time job.

I like the problems other people avoid, especially hunting down a bug until it’s actually fixed. Bilingual English / Spanish. Based in London.

Contact Get in touch

Hiring, or want to talk about a project? Send me a message. My CV is available on request.

Or email hi@cardini.dev