My Hackathon Journey: From Zero to Champion

Kurt McCarver — Wed, 01 Jul 2026 00:45:53 +0000

My hackathon journey didn't start with winning.

It started with losing.

My first hackathon was BlueHacks 2025. We spent almost all of our time building and very little time understanding the business side of our project. When it came time to pitch, we struggled to explain why our solution mattered. That experience taught me an important lesson:

A great product means nothing if people don't understand its value.

Next came GCash's invite-only hackathon.

We didn't win, but I walked away with something more valuable than a trophy. I learned more about product thinking, working with data, and met someone named Neo, who would later become a key part of my hackathon journey.

Then came the YSES Hackathon.

Once again, we fell short.

We believed we had built a strong solution, but we made the same mistake. We focused too much on the technology and too little on market validation, business models, and the value our product created.

Everything changed during Based Space Batch 002.

It was my first international blockchain hackathon, and it completely changed how I approached building products.

During the program, Sir Eli Becislao, then Country Lead of Base Philippines, emphasized the importance of storytelling, pitching, and business strategy. That was when I realized hackathons aren't just coding competitions.

They're startup simulations.

Our team eventually pivoted our idea and built NameThat, a Web3 platform on Base where users could earn rewards for creative names and ideas. Although we didn't win, we received the Most Pivoting Project Award, recognizing how much we improved our solution throughout the competition.

That experience became a turning point.

Next was the Philippine Blockchain Week ICP Hackathon.

Simply being selected as one of the Top 50 teams in the Philippines already felt like an achievement. Then we were invited to present FarmChain on the Philippine Blockchain Week stage.

When the results came out, we finished Top 6 out of 50 teams.

To some, sixth place might not seem significant.

To me, it was proof that we were growing. The lessons from every previous loss were finally showing in our work.

Then came GDG PUP Sparkfest 2025.

Remember Neo?

I reached out and invited him to join our team.

Together, we built CrowdCon, an AI-powered crowd safety solution that uses YOLO computer vision to detect signs of distress and help responders identify people who need immediate assistance during large events.

This was also where I met Joaquin, who challenged the way I thought about building products. He taught me that great ideas aren't enough. Sustainable products need strong business models, clear revenue strategies, and a deep understanding of the market.

By the end of the competition, CrowdCon won 1st Place and the DevCon Award for Most Feasible Solution.

My first major hackathon championship.

Most recently, we joined DLSU Hackercup 2025.

Our team built Klutch, a platform that connects people with trusted individuals who can help solve everyday tasks and problems.

We finished with 3rd Place.

Looking back, the biggest lesson wasn't about technology.

It wasn't about frameworks.

It wasn't even about winning.

It was realizing that the best products exist at the intersection of technology, business, and execution.

The teams that consistently perform well aren't always the ones with the most advanced code. They're the ones that understand the problem deeply, communicate their solution clearly, and build something people genuinely need.

If you're joining your first hackathon, don't focus on winning.

Focus on learning.

Focus on meeting people.

Focus on asking questions.

Focus on improving every time you compete.

Because every loss, every rejection, and every failed presentation is teaching you something that success never could.

Those experiences aren't setbacks.

They're preparation.

And as for me, I know I'm still only at the beginning of the journey.

I Built Fix My Folder Because My Downloads Folder Was a Disaster

Kurt McCarver — Wed, 01 Jul 2026 00:44:03 +0000

We've all been there.

You download a PDF for work, a ZIP file for a project, a few screenshots, random installers, and before you know it, your Downloads folder has turned into a place where files go to disappear.

I kept telling myself I'd organize it later.

I never did.

So instead of cleaning my folders manually every week, I decided to build Fix My Folder.

What is Fix My Folder?

Fix My Folder is a local Python desktop application that helps organize folders without making changes behind your back.

It scans a folder, categorizes files, builds a clear action plan, and lets you review everything before anything is moved, cleaned, extracted, or organized.

The goal was simple:

Make organizing files take seconds instead of minutes.

Why I Built It

This project started because I wanted to solve my own problem.

As someone who downloads documents, images, ZIP files, installers, and project assets almost every day, my Downloads folder became increasingly difficult to manage. Finding a file often took longer than it should.

I wanted something that could:

Scan a folder quickly
Categorize different file types
Help organize everything automatically
Still keep me in control before applying any changes

That became Fix My Folder.

What I Learned

This project reminded me that not every application needs to solve a global problem.

Sometimes the best projects come from everyday frustrations.

Building software for problems you personally experience makes it much easier to understand what users actually need because you're the first user.

What's Next?

I have a few ideas I'd like to explore:

More customization for organizing rules
Better cleanup suggestions
Improved user experience
Additional quality-of-life features

I'm planning to keep improving it over time.

If you've ever had a chaotic Downloads folder, I'd love to know how you manage it.