- Home
- 001-frontend-design
If you're a frontend dev and don't know design, you're already behind
if you’re a frontend dev and don’t know design, you’re not falling behind.
you already fell behind.
the market spent years saying frontend is about code. that all you need is a framework, architecture, best practices and consuming APIs.
the result? an entire generation of devs who only know how to install shadcn and pray nobody asks for something outside the template.
this isn’t an exaggeration. open any frontend job posting today. most ask for “experience with design systems” or “eye for UI/UX”. the market has already changed. most devs haven’t noticed yet.
the disc that changed my life
I’ve been working with design since I was 12 when my uncle gave me a Photoshop CS6 tutorial disc made by Adobe themselves.
that changed my life.
I didn’t know it at the time but that disc was the beginning of everything. I spent years learning composition, typography, visual hierarchy, color. things most frontend devs have never studied and might never study.
when I moved to development I didn’t become just another frontend. in 5 years of career, everywhere I went I was considered above average.
not because I was the best at code. but because I understood architecture, React best practices and also knew how to create animations, design systems and have visual opinions.
that combination isn’t common. and the market pays well for it.
”Design Engineer” isn’t a trend
“Design Engineer”. sounds trendy. sounds like a made-up title to impress recruiters. another gringo term that Brazilian twitter imported without context.
but what I see in practice is different.
I see dozens of extremely talented designers who learned frontend implementing features 10x better and faster than the average dev. I’m not talking about people who can center a div. I’m talking about people who understand why a button is 44px tall, why spacing between elements follows a 4px scale, why that animation needs 200ms and not 400ms.
while the average dev copies shadcn components without understanding why, the design engineer creates the design system from scratch. tokens, variants, visual hierarchy. everything with intention.
the difference isn’t talent. it’s repertoire.
20 minutes
yesterday I wanted to test a workflow in a project I’m launching soon.
I designed the complete flow in Figma. design system, component variants, tokens, everything. connected my Figma to an MCP and built the entire site respecting my code patterns and best practices.
total development time: 20 minutes.
and I’m not impressed by this. because it’s not magic. it’s what happens when you combine design fundamentals + code fundamentals + the right tools.
I’m not “using AI to replace devs”. I’m using the current system to deliver more and more in less time. because I have the foundation to do it.
and that’s the part people don’t understand. AI doesn’t replace fundamentals. it amplifies them. if you don’t have a foundation, the tool does nothing for you. if you do, it transforms you into a machine.
the part nobody likes to hear
now the part nobody likes to hear but you need to hear:
you “dev” cost money. your time is money.
why do you think Anthropic and Vercel give 5 thousand dollars in AI credits to their devs? that’s almost 30% of their average salary.
because if the dev is 50% faster the company is already profiting. the math is simple. and it works against those who are slow.
companies won’t wait for you to learn. they’ll hire someone who already knows. or worse, they’ll realize that one design engineer does in one week what two frontends did in a month.
the competition isn’t fair
the dev who only knows code will compete with the dev who knows code + design + knows how to use AI as leverage.
it’s not a fair competition. it never was. and it’s going to get worse.
Design Engineer isn’t a hype title. it’s the natural evolution of those who understood that frontend was never just about code.
you only have to gain by updating yourself. even if you’re a very above-average dev. because the ceiling for those who know design + code is simply another level.
so if you’ve never opened Figma with the intention of learning, start today. not tomorrow. today.
the market won’t wait for you to catch up.