My Story.

Like many kids, my first connection with technology came through games. At that time, I did not know what engines, rendering, servers, or algorithms were. I just knew that pressing a button and seeing a world respond felt fascinating. Over time, that curiosity changed from this is fun to how does this actually work?

I chose Computer Science because I wanted to understand technology properly. At first, it still did not feel like the interest I was looking for. A lot of it looked like math, loops, syntax, and assignments that felt far away from the systems I was curious about. I was learning, but I had not yet connected those basics to the kind of software that runs real products.

DevWeekends changed that for me. My mentors helped me see the bigger picture and introduced me to ideas that genuinely pulled my curiosity back in: how authentication works, why token-based and session-based systems exist, how APIs are designed, why databases shape products, and how architecture decisions affect reliability. I went from looking at the field through a web developer or app developer lens to thinking more like a software engineer.

That mindset shaped the way I approached my own projects. While building my multi-vendor e-commerce store, I started thinking beyond whether the feature worked. I began asking better questions. How should the backend be structured? How should different roles interact? How should orders, refunds, sellers, admins, events, coupons, chat, and payments fit together without becoming chaos?

I call myself the Boring Engineer because I have started to respect the parts of software that are not always flashy. Clean APIs. Predictable flows. Reliable state. Clear database models. Maintainable structure. These things may not look exciting in a demo, but they are what make software survive real usage.

I am still early in my journey, but my direction is clear. I want to become a software engineer who builds reliable, useful, and well thought out systems. At the same time, I am equipping myself with the right AI tools and knowledge: LLM integration, agents, retrieval workflows, automation, and the engineering judgment needed to use them well. That makes me optimistic about the future, not because AI replaces the fundamentals, but because it expands what a deliberate builder can create.