|

I'm a quiet observer by nature. Every so often, I step back, audit my life, and ask myself a simple question: what can I fix so tomorrow is a little easier—for myself, and maybe for someone else too? That habit has become the source of most of my projects. I collect problems, obsess over them, and build solutions—not because they're revolutionary, but because somewhere, someone might be facing the exact same struggle. If something I create saves even one person an hour of frustration, every late night spent building it was worth it.

I'm driven by an almost unreasonable curiosity. "It works" has never been an answer that satisfies me. If a computer runs on a CPU, I want to know how the CPU works. If it's logic gates, I want to understand the transistors beneath them. If it's transistors, I want to understand the physics that make them switch. I keep following the chain until I reach the lowest level I can. That curiosity is what led me into VLSI design and sparked a long-term goal: to build my own CPU—not just to create one, but to truly understand the machine that made me fall in love with computing in the first place.

I also believe there's no such thing as difficult—only unfamiliar. Because of that, I rarely look for shortcuts. I'd rather spend seventeen hours understanding a single bug than five minutes copying a fix. For me, the satisfaction has never come from getting the answer; it comes from understanding why it's the answer.