When most people learn to code, they focus entirely on the technical side. Master React. Learn TypeScript. Understand databases. And those are important — but they're only part of the picture.
The Code-Only Mindset
If all you know is code, you can build what someone tells you to build. But you can't decide what to build, how it should feel, who it's for, or why it matters. You're a tool operator, not a builder. And I want to be a builder.
I've seen technically brilliant apps that nobody uses because the UX is confusing. I've seen beautiful websites that don't convert because nobody thought about the user journey. Code alone doesn't make a product. Thinking does.
What Else Matters
- UI/UX Design — Understanding why certain layouts work, how colour affects emotion, and what makes an interface intuitive. You don't need to be a designer, but you need to think like one.
- Product Thinking — Who is this for? What problem does it solve? What's the simplest version that delivers value? These questions save you from building the wrong thing.
- Marketing & Business — If nobody knows your product exists, it doesn't matter how good it is. Understanding how people find, evaluate, and decide to use something is essential.
- Systems Thinking — How do the pieces fit together? How does the frontend talk to the backend? How does the infrastructure scale? Seeing the whole system makes you better at every part of it.
How I Study
I don't take formal courses in all of these. I read, I observe, and I build. When I visit a website I like, I don't just look at the code — I think about why the layout works, what the copy is doing, and how the user journey is structured. When I use an app, I pay attention to the micro-interactions, the onboarding flow, and the moments of friction.
"The best developers I've come across aren't the ones who know the most languages. They're the ones who understand why things are built the way they are."
The Compound Effect
Every skill compounds. Understanding design makes your code more intentional. Understanding business makes your features more valuable. Understanding marketing makes your projects more visible. None of these skills exist in isolation — they multiply each other.
I'm not saying you need to master everything. But if you only learn code, you'll always need someone else to tell you what to build and how it should look. And if you want to be a builder — a real one — that's not enough.
