Timestamped Thoughts

← All posts
Tech

#9 First hackathon/build night ever

· 2 min read

So I finally attended my first ever Hackathon / build night.
I was pretty mind-blown by it in fact!
Hackathon

Can’t wait for the next one already.

It was so inspiring to see others ideas, their finished demos.

I had an initial plan of working on my bike app Spoke Record, but later decided to work on HuddleUp gamification of sports idea. But I couldn’t do much out of it. Very bare minimum UI, so didn’t really have anything to present, maybe next time I would pick up speed and do better.

But the entire time I was there I was fully focused, worked on my project, drank, ate. Had a really good time. Even met another girl there, and we hit it off with our conversations I feel. Since there are very less girls at such events, I was glad I met her.
Hackathon

One of the presentations int_review was too good to be honest, their idea, presentation, execution, everything was on spot. A very memorable one indeed!
Hackathon

Here are the Github links of the projects that I really liked:

  1. https://github.com/GokulRajan23/Int-review
  2. https://github.com/suleman1412/lesson-forge
  3. https://github.com/josteng/Heft
  4. https://github.com/suleman1412/buildathon-claude

Here’s a pdf of all the demos of the night for easy short descriptions:
Lightning demos · Claude Build Night (PDF)

Also you should really check out this grill-me skill by Matt Pocock, I used it and found it to be really useful: https://github.com/mattpocock/skills Alexander Eiswirth suggested this skill to me, so thanks to him, learnt something new & useful!
Here’s a summary of the skill: Matt Pocock’s “grill-me” is a skill for AI coding agents (like Claude Code) that forces the AI to interview you about a task before writing any code, asking one clarifying question at a time instead of guessing at your requirements. It walks through decisions like edge cases and scope, offering a recommended answer for each, and only proceeds once you’ve confirmed shared understanding. It’s meant as a fast, lightweight planning step to catch ambiguity early, before it turns into wasted implementation work.

Ciao!