The author notes that vibecoding has entirely replaced coding in hackathons (where speed is essential, bugs are tolerated, and only the demo is judged). I agree.

But then says this means software is “solved” so only hardware hackathons matter. Why?

If anything, I think software hackathons have become more useful, because ideas have become more useful. Even if ideas are cheap, not everyone has 24-72 hours for a prototype, in a creativity-inducing space that may inspire better details.

And software isn’t solved: some ideas still require low-level knowledge and skill to translate into prototypes, especially if the hackathon judges require some functionality.

Whether your purpose of a hackathon is:

- Make a prototype, then if it seems useful afterwards rewrite it into a full product

- Make a prototype that seems useful to attract investors (whether you start a company that may not launch or apply to a company that wants your creativity)

- As an organizer, find ideas related to your company

- Have fun, enjoy free food and good company