The Designer Who Codes: My Journey to Software Engineering

I never planned to become a software engineer. Really.

As a designer at Consenso Labs, I was happy crafting pixels in Figma. But something kept bugging me - the gap between my designs and their final implementation. You know that feeling when you see your perfectly crafted design turned into something... different? Yeah, that was my daily struggle.

Why I Started Coding

It wasn't frustration that drove me to code. It was curiosity. I wanted to understand why certain design decisions were "impossible" to implement. 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 lost. HTML and CSS seemed straightforward enough - after all, they're just styling, right? (They were not just styling). But JavaScript? That was a different beast entirely.

The Learning Curve Was Real

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

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

But there's good news too.

The Designer's Advantage

Turns out, designers have some unique advantages when learning to code:

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

What I Wish I Knew Earlier

If you're a designer thinking about diving into development, here's my honest advice:

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

Where I Am Now

Today, I'm a software engineer at Reclaim Protocol. I don't actively design anymore, but I won't hesitate to fire up 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's like having a built-in design system in my head.

The best part? When I'm 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? Hell yeah. The ability to handle both design thinking and development has opened doors I didn't even know existed. But it's not for everyone, and that's perfectly fine. Some people prefer to specialize deeply in one area, and that's equally valuable.

Some Real Talk

If you're considering this path, remember:

It's not about becoming a "unicorn" - it's 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's 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're curious about code, take that first step. Just remember to bring your design sensibilities with you - they're more valuable than you might think.

And hey, if you're struggling with the transition or just want to chat about it, reach out to me on Twitter. I've been there, and sometimes it helps just to know you're not alone in this journey.