Senior Frontend Engineer / 2026
I build front ends that stay fast after they ship.
I'm Miguel, a senior frontend engineer in Colombia with 17+ years of experience. A performance habit older than any framework I use, and open-source code — one widget alone serves 11M+ requests a month.
Read the writing ↘02About
I taught myself to code with no formal training, then got my first professional job in 2009 and studied Multimedia Production at SENA while working. Since 2023 I've been back in school for a Software Engineering degree, alongside my day job as a senior frontend engineer at SilverAssist. I'm based in Madrid, Cundinamarca, Colombia. Outside of work, I'm usually out with my dog, Mila.
03What I do
The interesting part is never the first release. It's whether it still holds up a year later.
- 01
Performance that survives the release
96 desktop Lighthouse, 0.8 s LCP, 0 CLS on a production platform — and six years of the same work before the current stack, back to service workers and PWAs on storefronts.
- 02
Next.js platforms, nine of them
App Router, Server Components and Server Actions against headless WordPress and REST, shipped and maintained rather than prototyped.
- 03
Pipelines that catch things early
Matrix testing, CodeQL, Dependabot with auto-merge and SHA-pinned actions across 18+ repositories, plus CI that provisions and requests automated review.
04Writing
What each project actually taught me.
Not tutorials. The bug that took a week to find, the fix that turned out to be configuration, the assumption that measurement destroyed.
Taking minification offline: two Rust libraries, six platforms, seven languages
Moving my VS Code extension from a minification API to local Rust minifiers fixed every feature complaint I had, and shipped a package that only worked on my own laptop to a few thousand people who were not me.
Shipping seven languages and showing everyone English
My VS Code extension had shipped translations for seven languages since October. Nine months later I found out that six of those bundles had never been displayed to a single user, and that my i18n test suite had been asserting through the bug the whole time.
How I fixed the macOS bug that broke every VS Code extension's tests
My own extension's tests started failing on macOS. I chased the wrong cause first, then found someone else had already diagnosed the right one, and shipped the fix myself instead of waiting.
Building my first VS Code extension, from a web form to the Marketplace
I was minifying legacy WordPress theme files by pasting them into a browser tab. Here's how that turned into a published VS Code extension, and the tooling it took to get there.
05Contact
Have something to build, or just say hi.
Madrid, Cundinamarca, Colombia