Blog

Hey there

24 years old • he/him

In my early journey I studied computer science and worked as a motion designer with several companies and studios remotely, including Reline Studio. But honestly, something was missing - my animations felt static, they lacked the interactivity I was craving. I tried Rive, but it wasn't quite hitting the mark for what I wanted to create. After digging around for a while, I discovered React and its ecosystem, and everything clicked. The way you could build interactive experiences just felt right. So I mapped out my own roadmap and dove into web development as a frontend developer. Still learning, still building, still figuring things out.

How I Work

I don't like jumping into a project by asking AI to decide what libraries or tools to use, or to set up the architecture from scratch. I think that's where things usually go sideways. Instead, I start by really studying the business requirements - what actually matters, what the priorities are, what problems might pop up down the line, even things like where the customers are located and how that might affect performance. Once I have that context, I usually reach for shadcn and its Tailwind-based design system. What I really like about it is that it gives me the actual component code - not some locked package I can't touch. I can modify everything based on the UI requirements and design system I'm working with. They also use the OKLCH color space, which makes colors blend more naturally. My typical stack is Next.js, Tailwind, TypeScript, and shadcn components. But I'm not rigid about it. The architecture needs to be flexible enough to handle whatever changes come up later, because they always do.