Designers Don't Need to Learn Code — They Need to Learn AI
A friend asked me the other day: "You're a designer — why are you suddenly trying to code? Are you just chasing a trend?"
Fair question. And the answer is both yes and no.
Yes, because I did start from watching YouTube. Claude Code demos, Cursor tutorials, V0 showcases — all those AI coding tools. It looks like a trend from the outside.
No, because I'm not learning to code. I'm asking AI to code for me.
Big difference.
## Learning to code vs. asking AI to code
Learning to code means spending six months with JavaScript, understanding syntax, writing every line yourself, debugging until you want to snap your keyboard in half.
Asking AI to code means describing what you want, watching it build, reviewing the result, and telling it to fix what's wrong.
One is a skill investment. The other is a workflow. I chose the workflow.
## The designer advantage
Here's something I've been thinking about: when AI can write code, who has the real advantage?
Not developers — they already know how to code. AI just makes them faster.
The real winners are people who know what to build but couldn't build it before. People who understand users, design, and products. People like designers.
Think about it. A designer knows:
- >What looks good and what looks terrible
- >What's intuitive and what's confusing
- >Where users tap and where they give up
- >How to make something feel polished
These things take years to develop. They can't be prompted. They can't be generated. They're the hard-earned instincts that separate "technically works" from "people actually want to use this."
Code, on the other hand? AI writes it pretty well now. Not perfect — but good enough to ship.
## My first test
I decided to test this theory by building my personal website. I told Claude Code: "Build me a portfolio site. Dark theme, terminal aesthetic, with a blog and an art gallery."
It built the whole thing. I sat there reviewing the output, pointing out what looked wrong, what needed better spacing, what felt off about the interaction — doing exactly what a designer does.
The result: gianghaison.me — from zero to a live website in one day. I didn't write a single line of code. Not one.
## A disclaimer
I'm not saying designers are better than developers. That's nonsense. Good developers understand architecture, scalability, security, performance — things AI still struggles with at scale. If I were building a banking system or a self-driving car, I'd want a real engineer.
But for building small products? Apps for regular people? Tools that solve specific problems?
Design skills + AI coding is a surprisingly powerful combination. And I think we're just at the beginning of figuring out what's possible with it.
## What's next
I'm now building several products this way — Hũ Vàng (an asset tracker for Vietnamese users), FlashKid (English flashcards for kids), and more. All solo. All with AI.
Will it work? I genuinely don't know. But the experiment is worth running.
I'll keep sharing what I learn here. The wins, the failures, and everything in between.
Previous post: The Challenge: A Designer Building Products with AI in 2026