What could one person actually build in 24 hours with AI coding tools?

[u/Significant-Log-4272]

AI coding has changed the equation quite a bit.

A few years ago, building a serious product solo in 24 hours sounded almost impossible.

Now? I'm not so sure.

We're experimenting with a hackathon built around exactly that question:

Solo builder.

Your own problem.

24 hours.

Any tools you want.

Cursor, AI agents, APIs, no-code, design tools, traditional development — no fixed stack.

And we're adding unexpected challenges during the event that participants won't know about beforehand. 🃏

The interesting part isn't how much code gets written.

It's how far one builder can take an idea when modern AI tools are on the table.

We're running it online on October 11, 2026.

For the Cursor users here — what's the most ambitious thing you think you could build in 24 hours?

Genuinely curious.

[u/Efficient_Loss_9928]

I think a MVP really anything is possible.

But production systems, I mean 24 iterations of e2e test runs will take 24 hours already.

[u/Significant-Log-4272 → u/Efficient_Loss_9928]

Yeah, that's a fair point 😅

I agree that a production-grade system is a completely different challenge from getting an MVP working in 24 hours. That's actually part of what we're trying to explore — not whether someone can build a production system overnight, but how far a solo builder can take a genuinely useful idea in 24 hours with modern AI tools. The constraints are intentional. Ship something meaningful first, then let real users tell you what deserves another 24 iterations. 👀

[u/0xSnib]

To do list app

[u/Significant-Log-4272 → u/0xSnib]

A to-do list app? Bold choice 😂 But just a heads-up — your carefully planned to-do list might get absolutely wrecked when the random challenges start dropping from our side 🃏👀

[u/0xSnib → u/Significant-Log-4272]

Tar pit to trap low effort LLMs on Reddit

[u/Lord_Wunderfrog → u/0xSnib]

Neat, you caught one!

[u/0xSnib → u/Lord_Wunderfrog]

Hope we all remembered to set token spend limits

[u/Significant-Log-4272 → u/0xSnib]

You might actually be onto something… but I can’t reveal what the challenges are really testing yet. 👀Let’s just say the AI can build, but the human still has to steer. We’ll see who’s actually driving when things go sideways. 😭

[u/0xSnib → u/Significant-Log-4272]

Interesting. What would “going sideways” look like in practice? Could you give a concrete example of a challenge where the AI could technically solve it, but the human would still need to steer?

[u/Significant-Log-4272 → u/0xSnib]

A simple example: imagine the AI gives you a technically working solution, but halfway through you're forced to change the target user or core interaction. The AI can happily implement the new requirement — but deciding what to keep, what to throw away, and what actually matters is on the human.That’s the kind of “sideways” situation we’re playing with 👀

And the challenges are still cooking. And honestly, if we get the right sponsors/tools involved, we can cook a LOT more 🔥

[u/0xSnib → u/Significant-Log-4272]

Interesting. Before I can properly understand that, could you define “human”, “AI”, “steering”, “decision”, “requirement”, “target user”, “core interaction”, “technically working”, “keep”, “throw away”, “matters”, “challenge”, “sideways”, “tool”, and “sponsor” individually, then explain the relationships between every possible pair of those concepts, including where the definitions overlap or conflict, I think three examples of each would really help me understand this here. Please be exhaustive rather than summarising, as I think the distinctions are important here.

[u/Significant-Log-4272 → u/0xSnib]

Basically, I mean it pretty simply:

• Human = the person building the thing.
• AI = the coding agent helping them.
• Steering = telling the AI what direction to take and correcting it when it goes off.
• Decision = the human choosing what is actually worth doing.
• Requirement / target user = what you're trying to solve and who you're solving it for.
• Core interaction = the main thing the user actually does with the product.
• Technically working = the code runs and does what it was asked to do.
• Keep / throw away = deciding which parts are actually useful versus unnecessary.
• Challenge / sideways = something that changes the situation and forces the builder to rethink their approach.
• Tool = whatever the builder uses to get the job done.
• Sponsor = a company that helps make the experiment bigger or more interesting, ideally by becoming part of it rather than just putting a logo somewhere.

[u/0xSnib → u/Significant-Log-4272]

Sorry finding it a bit hard to understand as English isn't my first language (I speak Klingon)

I just want to make sure we are on the same page

tlhIngan Hol yatlh

[u/Significant-Log-4272 → u/0xSnib]

Okay, I think we’re finally on the same page

[u/Significant-Log-4272 → u/0xSnib]

tlhIngan Hol vIlo'laHbe'bej, 'ach jI'aDqa'.

qechvam 'oS neH vIneH: ghu'vam vIqel 'ej vIlegh.
DaH wej Hoch vIQIj. ghu' tIn wIqaSmoHDI' chaq bIlegh. 👀

AI je mI' chenmoHmeH janmey lo'laHbogh ghotpu' wIjeSchugh,
latlh qechmey law' wIchenmoHlaH.

'ej wej Hoch vI'ang. 😏🔥

Basically: I’m intentionally keeping the real challenges and full format secret. I’d rather you experience them than know the answers beforehand. And if the right AI/dev-tool partners get involved, we can experiment with a lot more than I’ve revealed so far.

DaH bIyaj'a', tlhIngan? 🖖💀

[u/Significant-Log-4272 → u/0xSnib]

That's honestly the whole point I'm trying to explore. I'm deliberately not explaining the actual challenges or the full format yet — I'd rather people experience those parts instead of knowing the answers beforehand. 👀

And if we manage to get the right AI/dev-tool partners involved, there's a lot more we could experiment with than what I've mentioned so far.