Here's more about me

My interest in programming started the first time I wrote HTML and CSS and saw a blank page turn into something real. That moment—creating something from nothing but code—was what pulled me into software development. At first, my relationship with technology was mostly through gaming. I spent a lot of time on my laptop and originally thought studying IT would simply keep me close to that environment. But once I started learning how systems actually worked and began building things myself, the focus shifted. What used to be time spent playing games became time spent learning how to build software. Over time I built small websites, desktop applications, and school projects, but the moment that confirmed everything for me was when I built my first mobile application. That project made it clear that this was the field I wanted to pursue long-term. Building software stopped being an academic activity and became something I genuinely wanted to keep doing.

How I Work

One thing that tends to define how I approach development is persistence. When I run into a problem, most people recommend stepping away and taking a break. I’ve tried that approach many times, but it rarely works for me. When a bug or error exists in something I’m building, my mind keeps returning to it until it’s solved. Instead of stepping away, I usually push harder. I investigate the problem, test different approaches, read documentation, and keep debugging until I understand what’s actually happening. The moment when a difficult bug finally gets resolved is one of the most satisfying parts of being a developer. That process—struggling with a problem until it makes sense—is how I’ve learned the most.

My Learning Style

I strongly believe in project-based learning. Rather than spending long periods planning everything perfectly before writing code, I often start building early and learn along the way. Some developers prefer heavy planning before implementation. For me, the act of building is what reveals the real problems and forces me to understand systems more deeply. This approach means I encounter mistakes and obstacles during the process, but those experiences tend to produce the strongest lessons. Outside of school projects, I spend a lot of time working on personal projects, experimenting with new tools, and studying technologies related to the work I want to do. By the time new topics appear in the curriculum, I’ve often already explored them on my own.

My Reputation Among Peers

In group projects, I usually end up taking the role of both team lead and primary developer. Part of that comes from the extra time I spend studying and building outside the classroom. Classmates often describe me as passionate and hardworking. Some of them see me as “the smart one,” although I’m not always convinced that’s accurate. If anything, I think I’m just very persistent and willing to put in more hours trying to understand something. Even when I feel uncertain about my abilities, I keep pushing forward. That combination of curiosity and discipline is what drives most of my progress.

What Good Software Means

For me, good software is software that people can use without confusion. A user shouldn’t need instructions from the developer just to understand how an interface works. Navigation should feel natural, actions should be predictable, and the system should behave consistently. Clarity is one of the things I care about most when designing interfaces or writing code. Another part of building good software is anticipating edge cases. In practice, this is often where things break. Even when I think I’ve accounted for everything, demos and real use often reveal unexpected issues. Those moments can be frustrating, but they also remind me that good engineering requires constant refinement.

What I'm Currently Focused On

My Long-Term Vision

In the long term, my goals are both professional and personal. Professionally, I want to continue building applications and systems that have real value. I’m particularly interested in creating software that has meaningful impact rather than simply existing as technical demonstrations. Personally, my motivation is tied closely to my family. One of my biggest goals is achieving financial stability and having the freedom to support the people who matter most to me. I want to reach a point where I can provide security, stability, and opportunities for my family while continuing to grow in my career. Everything I’m building now is part of that larger goal.

What Drives Me

If I had to describe the main thing that differentiates me from other developers at my level, it would probably be how strongly I care about the work. When I enjoy what I’m doing, my motivation increases significantly. I tend to invest more time, explore deeper solutions, and push myself harder than expected. That persistence is something I rely on heavily. Skill develops over time, but work ethic is something that shapes progress every day.

The Kind of Environment I Thrive In

I perform best around other developers who are building and improving constantly. Being surrounded by people who care about solving problems and writing better code pushes me to raise my own standards. Those environments accelerate growth.