I started my career on the design side.
I enjoyed figuring out layouts, working with typography, and turning ideas into something people could see and interact with.
But over time, I became more interested in what happened after the design was approved.
How does it actually work? How does it behave on different screens? What happens when the content changes? Can we make it faster?
Those questions gradually pulled me deeper into development.
Today, I work across both design and code, and I think the combination makes a real difference.
A design file is only the beginning
It's relatively easy to make something look good in a static mockup.
The real challenge begins when that design needs to work in a browser.
Text wraps differently. Images change size. Content grows. Buttons need real actions. Animations need to feel smooth without slowing everything down.
These things are easy to overlook when design and development are treated as completely separate jobs.
Because I work on both sides, I can think about these details much earlier.
If I know a particular interaction will be difficult to maintain, I can find a simpler approach before spending hours polishing it.
And if something isn't working during development, I can adjust the design without losing the original idea.
Fewer gaps between the idea and the finished product
One of the biggest advantages of designing and building something myself is continuity.
The thinking doesn't stop when the design is finished.
I can carry the same attention to detail through the frontend, functionality, responsive behavior, and final testing.
That doesn't mean every project needs one person doing everything. Larger products often benefit from specialists working together.
But for many websites and digital products, having design and development closely connected can make the process much more straightforward.
Technology should serve the project, not the other way around.
Good development should support good design
I work with technologies like React, Next.js, and modern frontend tools, but I don't think clients should need to care about the technology just for its own sake.
What matters is whether the website is reliable, easy to update, fast enough for its purpose, and capable of growing with the business.
Technology should serve the project, not the other way around.
That's how I approach my design and full-stack development work: understand what needs to be built, make sensible decisions, and pay attention to the finished experience.
From an idea to something real
For me, the most satisfying part of a project is seeing it move from an early conversation to a working product.
Not just a polished design file.
Something real that people can open, use, and benefit from.
That's why I enjoy working across both disciplines.
