Not too long ago, I stumbled upon a LinkedIn post by Yangshun Tay, the founder of GreatFrontEnd. His advice was simple but profound: if you want to stand out, learn complementary skills. You might not be the absolute best programmer in the world, and you might not be the world's best designer, but combining those two skills makes you exponentially more valuable.
As a full-stack developer who spent most of my time dealing with internet programming, databases, and APIs, this thought really lingered in my mind. I decided to act on it and enrolled in a web design course.
That course fundamentally shifted my perspective on software engineering. I realized that design is wildly underrated in the engineering community, and most developers make a critical mistake by completely ignoring it.
The Misconception of Design
Most engineers treat design as an afterthought. We obsess over building the next feature, optimizing database queries, and setting up scalable architectures. When it comes to the user interface, we often just slap on a UI library, adjust a few colors, and assume the job is done.
We tend to think of design merely as aesthetics—the typography, the spacing, the hex codes.
But as Steve Jobs famously said:
Most people make the mistake of thinking design is what it looks like. People think it’s this veneer—that the designers are handed this box and told, 'Make it look good!' That’s not what we think design is. It’s not just what it looks like and feels like. Design is how it works.
Working Backwards from the User
This philosophy is the secret weapon behind the most successful technology companies in the world.
Think about Apple, Airbnb, Vercel, or Linear. What separates them from their competitors isn't just their underlying technology. It is their unwavering commitment to a design-first culture.
The mistake most engineering teams make is starting with the technology. They build a complex backend, expose an API, and then try to figure out how to force a user interface on top of it.
Companies like Apple do the exact opposite. They start with the user experience. They ask: How should the user feel? What is the most intuitive way for a human to interact with this? Once that ideal experience is defined, they work backward to the technology, figuring out what code needs to be written to make that experience a reality.
This approach is why Apple's brand value is astronomical. It's why their logo isn't just a picture of an apple, but a symbol of trust, intuition, and seamless functionality.
Design is Logic
When you realize that design is how a product works, it stops being an art project and starts becoming an engineering discipline.
A well-designed website isn't just beautiful; it is intuitive. The user doesn't have to guess where the settings page is, or how to submit a form. The friction between the user's intent and the software's execution approaches zero.
When you learn design as an engineer, you stop building features in a vacuum. You start building experiences. You begin to understand that a lightning-fast backend is entirely useless if the user is too confused to click the right button.
Combining engineering execution with design intuition is a rare superpower. It bridges the gap between what a computer can do and what a human actually wants. If you are a developer looking for an edge, stop building features for a moment—and start learning how to design.