Your choice of tech stack can be make or break at a Hackathon. It can be the difference between rapidly iterating on an app in a fun domain, or tearing your hair out because it just-won't-build.
So when your team comes to the dreaded "what stack should we use?" discussion, we need some criteria to make that decision.
First, let's describe what kind of tech we want to use at a hackathon.
Hello world! quickly. We've on a deadline. We want project generators, templates, and one-click setups. We want example code that can be easily copy-pasted.
This is a bit of a hot-take, but I think rapid prototyping tools have improved dramatically in the last few years. They offer the right mix of high-level composability to smash out straightfoward tasks with enough low-level flexibility when you need to stray off the beaten track.
<aside> 💡 You can win a hackathon using a rapid prototyping tool. They are emblematic of the hack aspect of the competition. Don't do more work than you need to.
Heres what I recommend: