The Ultimate SRM Hackathon Survival Guide

Surviving a 36-hour hackathon at SRM requires more than just coding skills. It requires strategy.

1. Idea Validation First

Don't spend 20 hours coding a feature nobody wants. Spend the first 2 hours verifying that your idea actually solves a problem. Talk to mentors early.

A working prototype of a simple idea will always beat a broken prototype of a complex idea.

2. The Tech Stack

Stick to what you know. A hackathon is not the place to learn a new framework from scratch unless you want to spend 30 hours reading documentation.

• —Use Next.js for rapid frontend development.
• —Use Firebase or Supabase for instant backends.
• —Tailwind CSS is your best friend for quick styling.

3. Sleep is Not For the Weak

Pulling an all-nighter might sound cool, but your cognitive function drops massively after 24 hours. Take 3-hour shift naps.

Remember: Drink water, take breaks from the screen, and actually present your project with confidence.