> For the complete documentation index, see [llms.txt](https://til.aldrinjenson.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://til.aldrinjenson.com/talks-and-recognition/being-a-judge-at-hack4tomorrow-hackathon.md).

# Being a judge at Hack4Tomorrow hackathon

I was fortunate to be invited as a Judge for the Hack4Tomorrow hackathon conducted by Excel 2023

This was a nice new experience.

From participating in hackathons to Organizing them to now finally Judging one!

<figure><img src="/files/evvz6l7ZQ9ceXwzRnm6g" alt=""><figcaption><p>With Rindish Krishna, Afnan, Vishruth, and Abid Omar - my fellow judges. Cool people</p></figcaption></figure>

<figure><img src="/files/CsJbU6A23fw5jHe7U5Kx" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/ufSU6hbz8ZP5vXhCMoiI" alt=""><figcaption></figcaption></figure>

It was a good hackathon. Nice projects

After discussing among the judges, we finalized a few projects for the prize money. But I felt a bit sad thinking of the other teams who didn't win. I don't think I'd want to go into judging again if possible. The judges may have valid reasons to select certain projects, but it's hard for other participants to directly understand them I feel. Especially since they spent so much effort in the past 24-48 hours on their work in the hopes to win the prize.

Since I've been on both sides, I personally would prefer to stay against judging I think.