The Designer Who Codes: My Journey to Software Engineering

Koushith

I never planned to become a software engineer. Seriously.

As a designer at Consenso Labs, I was happy making pixels in Figma. But one thing was always bothering me. The gap between my designs and final code. You know that feeling when you see your perfect design turned into something different? That was my daily struggle.

Why I Started Coding?

It wasn't frustration that made me code. It was curiosity. I wanted to understand why some design decisions were "impossible". Why did developers keep saying "that's not how React works" when I asked for specific animations?

The first time I opened VS Code, I was fully lost. HTML and CSS seemed simple enough. They are just styling, right? (They were not just styling). But JavaScript? That was a totally different monster.

The Learning Curve Was Real

Here is what nobody tells you about switching from design to development:

  • Your design skills can actually slow you down at first. You will waste hours trying to make something pixel-perfect when you should be focusing on making it work
  • You will try to solve everything visually before thinking about data structures (spoiler: bad idea)
  • The impostor syndrome hits differently. You are not just a beginner, you are a designer who "should" know better

But there is good news too.

The Designer's Advantage

Actually, designers have some unique advantages when learning to code:

  1. We already think in components and systems
  2. We understand user flows and edge cases
  3. We can spot visual bugs from a mile away
  4. We know why accessibility matters, not only how to implement it

What I Wish I Knew Earlier?

If you are a designer thinking about diving into development, here is my honest advice:

  • Start with the basics. Yes, React is cool, but learn HTML/CSS properly first
  • Build stuff you have designed. It is more motivating than generic tutorials
  • Don't abandon your design skills. They are your superpower
  • Get comfortable with being uncomfortable. You will be a beginner again, and that is okay

Where I Am Now?

Today, I am a software engineer at Reclaim Protocol. I don't actively design anymore, but I won't hesitate to open Figma when needed. These days, I prefer to code directly in the browser. My design background has given me this intuitive sense of spacing, typography, and visual hierarchy that makes it possible. It is like having a built-in design system in my head.

The best part? When I am building features, I can anticipate design challenges before they become problems. That designer's eye never really goes away. It just evolves into this unique superpower where you can think about both user experience and technical implementation simultaneously.

Is it worth it? Definitely yes. The ability to handle both design and development has opened so many doors. But it is not for everyone, and that is perfectly fine. Some people prefer to specialize deeply in one area, and that is equally valuable.

If you are considering this path, remember:

  • It is not about becoming a "unicorn". It is about understanding both sides of product development
  • You don't need to be the best developer; your unique perspective is valuable
  • The journey is long, and that is okay. Take it one commit at a time

The tech world needs more people who can bridge the gap between design and development. If you are curious about code, take that first step. Just remember to bring your design sensibilities with you. They are more valuable than you might think.

And hey, if you are struggling with the shift or just want to chat, reach out to me on Twitter. I have been there, and sometimes it helps just to know you are not alone.

Used LLMs to correct grammar, typos etc 🤖

See all posts