I learned to code first. Then design taught me what to build.

I've been coding for a while. I started with Python when I was about ten, then picked up other languages over the years. What pulled me in was making things I could actually share and sell: apps and small web programs. I'd find a problem, often something I read about in the news affecting people somewhere in the world, from Europe to Africa, anywhere, and build something for that niche.

But after launching, the apps never looked great. That's when it hit me: the code working isn't enough. For people to actually use something, the design has to carry it. So I went to SCAD to study UX design, not as a side skill, but properly, so I could apply it across software and hardware.

What I learned there was that craftsmanship is everything. The detail is the product. When I was only coding, I couldn't see the gap between it works and people use it: the small font choices, the interaction details, the things you don't notice until they're wrong. That gap was the whole difference.

But even good design wasn't enough to do everything I wanted. I could build it and make it beautiful, and it still wouldn't reach anyone unless I could market it. The motion work I kept seeing in ads and launch videos was on another level; it caught my eye instantly and made me get the product in seconds. So now I'm learning After Effects and motion design too.

Code, then design, then motion. Each one filling a gap the last one couldn't. That's how I ended up a design engineer. And this site is the proof: I designed and built all of it myself.