My journey into engineering started with a simple question: how does this work, and how could it work better? I was drawn to anything that let me build something and then improve it — that curiosity is what led me to Mechatronics Engineering, where mechanics, electronics, and code all meet in one place.

​

Along the way, the real lessons came from the moments things didn't go as planned. Lab projects, machining parts by hand, troubleshooting under a hackathon clock — each one forced me to slow down, think through the failure, and try again. I learned that progress rarely happens in a straight line; it comes from iterating until something finally clicks.

​

That's shaped how I approach everything now. A new technique, an unfamiliar process, a tool I've never touched — I treat all of it the same way: get hands-on, expect to get it wrong a few times, and pay attention to what the mistakes are actually telling me.

​

What drives me is watching an idea become something real. Every project teaches me a little more about engineering — and about how I think. The story's still being written, but it's already taught me more about persistence and problem-solving than any one class could.