I've Graduated, But at What Cost? The Reality Check Beyond the Degree

I’ve graduated.

Yet holding the diploma in my hands, it didn't feel like some cinematic, triumphant victory. If anything, my mind immediately jumped to that classic Luigi meme with the caption: "I've won... but at what cost?"

Throughout my university years, I was never an exceptional student. My grades were totally fine, but I certainly didn't stand out at the top of the class. I always knew I enjoyed mobile development, but there’s a sobering lesson you eventually learn: liking something doesn't automatically mean you're skilled at it. And that reality hits hard when college life starts winding down and the real world stands waiting outside the auditorium doors.

The Attendance App and The Reality of Debugging

During my internship, I took on the responsibility of engineering a mobile attendance application, which eventually served as the foundation for my final graduation thesis.

It wasn’t a flawless journey. Things broke constantly. Buttons failed silently, state went out of sync, location validations threw unexpected exceptions, and local storage corrupted data during device rotation. Early on, I spent significantly more hours staring at stack traces and debugging than actually implementing shiny new features.

At first, that cycle drove me crazy. I felt like a fraud who couldn’t even write a straightforward screen without triggering three separate error dialogues. But with time, an important realization dawned on me: debugging isn't an annoying interruption of the job: debugging is the job. Tracing errors, understanding system limits, and systematically resolving issues you didn't fully comprehend five minutes ago is the literal essence of software engineering.

Tunnel Vision and The Trap of Waiting

My real mistake during college wasn’t making errors or introducing bugs. My real mistake was falling into severe tunnel vision. I spent months obsessing over micro-optimizing one single project, completely blind to how vast the broader developer ecosystem was and how much more foundational knowledge I still lacked.

Somewhere along the way, I stopped believing in the myth that a university degree would magically swing doors open for me. I stopped waiting for external validation and started asking myself a much simpler, more honest question: Why wait around, when you can just start building?

Sheesh, with only me fighting this battle, I honestly don't always know if I'm going to make it big. But everything worthwhile has to start somewhere. That is why I made the deliberate decision to share my journey and progress in public. Not to curate a glossy, fake motivational story, but to put real output on the table: what I build, what breaks, and what actually improves over time.

Build, Fail, Learn, Repeat

The most dangerous trap an aspiring developer can fall into is waiting until they "feel ready." If you wait until you feel fully prepared, you will sit on the sidelines forever. I finally understood that I will probably never feel 100% ready. But even if I'm never fully ready, I can always become better, sharper, and more resilient tomorrow than I was today.

Build. Fail. Learn. Repeat.

That brutal, beautiful feedback loop taught me more about software engineering than any semester in a classroom ever could. (Huge thanks to Dead Cells for ingraining that mindset into my psyche).

What’s Next

Now that graduation ceremonies are packed away, the roadmap ahead is clear and straightforward:

• Get significantly better at Flutter and reactive architecture.
• Ship more real-world, functional applications that solve concrete problems.
• Land a full-time role as a Junior Mobile Developer where I can contribute and grow.

College is officially behind me. From here on out, my progress is measured exclusively by the software I ship into the world, not by the paper certificate hanging on the wall.