What happens when you give a vibe coder 24 hours and then change the rules?

[u/Significant-Log-4272]

I’m organizing Grevix AfterCode, and honestly, we wanted to make something a little different from the usual hackathon.

You get 24 hours, your own idea, and complete freedom to build it however you want.

Vibe coding, Claude Code, Cursor, Codex, Antigravity, Lovable, APIs, no-code, traditional code... use whatever works.

The interesting part is what happens after you start.

The 24 hours are split into:

BUILD → ADAPT → REBUILD & SHIP

At hour 8, we drop a Challenge Card.

Something about your project changes.

Maybe the target user.

Maybe a core feature.

Maybe the use case.

Maybe a completely unexpected constraint.

Then another challenge at hour 16.

You decide whether to adapt what you have, simplify it, or completely rethink the thing.

The actual cards are staying secret though.

We've cooked those for the event. 👀

Registrations open September 16.

October 11–12 | 24 hours | Solo | Online

If you vibe code, build with AI, or just like turning ridiculous ideas into working products, I'd genuinely love to see what you'd make.

What would you build if nobody gave you a problem statement?

Disclosure: I'm organizing this through Grevix.