But the number 8 also refers to the team structure. Each X8 squad is limited to exactly 8 builders: 3 devs, 2 designers, 1 PM, 1 DevOps, and 1 wildcard. We sat down with the organizers to break down what makes this iteration different: 1. The "No-Ghosting" Rule In longer hackathons, half the team checks out by hour 30. In X8, there is no time to disappear. Every commit matters. Every design pixel counts. The rule is simple: If you don’t push code in the first 90 minutes, you’re buying coffee for the other seven. 2. The Stack is Fixed To save time on the dreaded "Which database should we use?" debate, HackShack X8 mandates a pre-approved stack for each event. For the fall series, the stack is Next.js 14, Supabase, and Tailwind. No arguments. No NIH (Not Invented Here) syndrome. Just building. 3. The 8-Minute Pitch You don’t get a deck. You don’t get slides. You get 8 minutes to show a working prototype. If the API fails in front of the judges, you don't get a retry. This is live. This is X8. Why "X8" is a Game Changer for Burnout We’ve all been there: A 48-hour hackathon ends, you win a $100 gift card, and then you sleep for 14 hours straight. You feel terrible. Your code is spaghetti.
Are you ready to build in 8 hours? Let us know in the comments. Want to host a HackShack X8 in your city? The blueprint is open source. Check the link in our bio for the rulebook. [End of post] 👉 If this was about a specific product (e.g., a new laptop model, a crypto exchange, or a gaming PC), please reply with the context and I will rewrite the post completely for accuracy.* hackshack x8
If you’ve been following the underground builder scene, you know that HackShack has always been the renegade sibling of the traditional hackathon. But X8? This is a complete reboot of the format. But the number 8 also refers to the team structure