10+ years building for the web. Most of that time I've been doing one thing: finding why frontend teams get stuck, and fixing it structurally.
I work between what the business needs and what developers can actually build. I look at the system, find the parts that aren't carrying their weight, and rebuild them so the team can ship without burning out.
Most frontend problems don't get solved by pushing harder. They get solved structurally. That's the work I do.
┌────────────────────┬────────────────────┬────────────────────┐
│ 10+ years │ 6 teams │ 12 products │
│ building for web │ scaled and led │ shipped │
├────────────────────┼────────────────────┼────────────────────┤
│ 1.1k+ stars │ 5,000+ devs │ 6 years │
│ Puppertino │ using Puppertino │ maintaining it │
├────────────────────┼────────────────────┼────────────────────┤
│ 90% faster │ 100+ clients │ 450MB cut │
│ MapVX 8s to 0.8s │ multi-tenant SaaS │ load 2-5min to <1s │
└────────────────────┴────────────────────┴────────────────────┘
I lead frontend teams and own design systems end to end. Strongest in CSS architecture and the work that keeps a codebase from turning into a house of cards. Ship production in Angular, WordPress, and Astro. A good system isn't sealed shut. It lets you add new components and features without breaking what's already there.
Puppertino: six years in, still shipping. A CSS framework inspired by Apple's Human Interface Guidelines. 10 component systems, the full Apple color palette, zero dependencies. Opinionated by design: fixed spacing scale, curated palette, macOS look out of the box. Used by 5,000+ developers.
Glassworks: liquid glass on web. A fork of LiquidGL rewritten on Snapdom. The original couldn't ship on the elements we needed at work, the upstream PR didn't make it, so I forked it and rebuilt it the way it had to be.
A multi-tenant platform serving 100+ clients. The codebase fragmented every time we onboarded a new client. I moved the personalization layer into a runtime API so the architecture stopped multiplying, and we shipped 50 site compilations in a single night. The business could finally scale to the number of clients sales was selling.
A 2-to-5-minute load became under a second. An app was choking during sales demos. I traced 450MB of dead weight, cut it, and got the first paint under a second. The contract closed right after.
Leadership is elevating the people around you. I run a lot of one-on-ones, ask devs what the boring repetitive stuff is, and build systems around those answers. A CEO once called me "the coach of his developers, and the organizer."
The mentorship part is what I care about most. Juniors and interns I worked with have grown into senior roles at companies they wouldn't have considered applying to two years earlier.
I write about problems I actually hit in real codebases:
- CSS Architecture for Enterprise: What Actually Works
- Why I Choose BEM Over CSS Modules (Most of the Time)
- SEO for Web Developers, the complete guide, updated for 2026
SEO is the one most frontend leads don't touch. I do. It's a structural problem, and developers are better positioned to solve it than anyone else on the team.
HTML, CSS/Sass, JavaScript, TypeScript, Angular, React, Vue, Astro, design systems, design tokens, GSAP, WordPress (custom), Laravel, Node.js, Figma, Storybook.
CSS isn't hard. People just reach for solutions from 10 years ago and get frustrated when they don't fit.
Spanish (native), English (C1, fluent professional). Started in Venezuela where I learned to build under real constraints. Then Colombia. Now Buenos Aires.
Looking for: Design Engineer or Frontend Tech Lead roles, fully remote. Most interested in teams that care what their product feels like, not just what it does.
codedgar.com · LinkedIn · GitHub · Dev.to · @codedgar_