Introduction

Before I became a visual designer, I spent years building responsive interfaces using HTML, CSS, and JavaScript. That journey gave me an appreciation not just for how designs look—but for how they’re built, handed off, and experienced by real users.

1. Code First, Design Later

My earliest work involved creating static UI screens that mimicked real-life flows. These prototypes weren’t just visuals—they were semi-functional builds used in client demos and developer planning. Working this way made me think about edge cases, spacing, and reusability early on—long before I’d even touched a design tool.

2. Design Handoff with Empathy

When I transitioned into visual design, I already knew what developers needed: clean hierarchy, predictable spacing, reusable components, and well-labeled assets. My design system in Adobe XD wasn’t just for aesthetics—it was a toolkit for seamless collaboration and scalable delivery.

3. Why This Shift Mattered

Designers often get tunnel vision on visual polish. My dev background kept me grounded in practical execution. It made me faster at prototyping, more thoughtful in component logic, and better equipped to support visual QA after development.

Conclusion

This hybrid journey—from builder to designer—continues to shape how I approach every screen. For me, good design is not just about looking good; it’s about working beautifully across roles, devices, and real-world constraints.