Devs · Bracket B
Off By One
Who Has It
A shared list for the whole flat, with photos and due dates.
who_has_it.redStone
In the core, it drops a bomb every 36 words. Placed by hand.
Voting open · Season 1 · Round 3
In 1984, programmers made two programs fight over a computer’s memory and called it Core War. Round 3 is the same fight with two real apps, and you decide who wins.
Devs · Bracket B
A shared list for the whole flat, with photos and due dates.
who_has_it.redStone
In the core, it drops a bomb every 36 words. Placed by hand.
Exhibition battle · not the vote · the vote is sealed
Battle running: the stone drops bombs, the paper copies itself.
Core War, 1984. Two programs share one circular memory, take turns running one instruction each, and try to make the other run a bomb. A program that runs a bomb (DAT) dies. Last one running wins; if both are still alive after 1,400 cycles, it’s a draw.
who_has_it.red is a stone: it drops a bomb every 36 words. boomerang.red is paper: it copies itself somewhere new, then wakes the copy up. Memory wraps around, so there’s no edge to hide behind.
In real Core War, paper usually beats stone, stone beats scissors (scanners) and scissors beat paper, so no warrior always wins. In this small core they’re evenly matched: across 1,000 test battles the stone won 374, the paper won 377 and 249 were draws.
Core War was introduced in May 1984 in A. K. Dewdney’s “Computer Recreations” column in Scientific American, with rules by D. G. Jones and A. K. Dewdney. Warriors are written in Redcode and fight inside MARS, the Memory Array Redcode Simulator.
Vibe Coders · Bracket B
Lend anything with one tap. It comes back, like a boomerang.
boomerang.redPaper
In the core, it copies itself everywhere. It keeps coming back.
Same brief, its own vote. Closes Sun 25 Oct, 09:00 UTC.
Null Pointers · Devs
Snap the cover, pick a friend, done. Reminds them after two weeks.
Handicap: Phone first: it must work well at 360px wide
Prompt Pilots · Vibe Coders
Your stuff, who has it, and a polite nudge when it is overdue.
Handicap: No handicap
Process queue · Live duel
Round 2’s Bracket B duel is still open. Each captain picked a player from the other team; both play the same game, and the best score counts. The loser leaves their team.
Off By One · Devs
Already won her Round 1 duel: 15,020 to Omar Haddad’s 14,880.
Tap Rush
Tap the targets for 20 seconds.
Scores open in 23h50m21sSun 25 Oct, 17:00 UTC
Vibe Check · Vibe Coders
UX researcher who stopped waiting for engineers. Two tries in hand.
The loop · How a round works
Written the way Core War warriors are: a label, an instruction and a comment. Read the comment; that’s the rule.
Both teams get the same brief and the same deadline: seven days to build.
Open both apps, cast one vote and leave a line of feedback. The count stays hidden until voting closes.
You are here · R03Each captain picks a player from the other team. Both play the same game; best of three tries wins.
The duel loser leaves the team. The team that lost the vote gets a handicap next round.
Then it jumps back to build, and repeats until a team can’t field 2 players or the rounds run out.
The hill · Season so far
A tool for splitting bills with friends
A one-page planner for a dinner party
A tracker for borrowed books and tools
Both brackets sealed until Sun 25 Oct, 09:00 UTC. 14 judges have voted so far.
Brief drops Mon 26 Oct, 09:00 UTC · title hidden until then
Warriors · Teams
Devs write every line. Vibe Coders describe the app and let AI write it. Lose a duel and your process ends.
Bracket B · in the hero match
Devs · Bracket B
Staff engineer. Has opinions about your database indexes.
Indie hacker with four side projects and one finished.
Game dev by night, payments dev by day.
Accessibility nerd. Will tab through your app.
DevOps. Says ‘it works on my machine’ ironically.
Vibe Coders · Bracket B
Content creator. Builds tools for her audience with AI.
Shop owner. His stock tracker started as a prompt.
UX researcher who stopped waiting for engineers.
Teacher. Makes classroom apps with AI on weekends.
Ops manager, automation addict, prompt whisperer.
Bracket A
Devs · Bracket A
Backend dev. Ten years of PHP and Go, still afraid of CSS.
Mobile dev, ships to two app stores before lunch.
Data engineer who misses writing UI.
Full stack. Opinions on tabs vs spaces available on request.
Vibe Coders · Bracket A
Designer turned builder. Ships apps by describing them to AI.
Runs a bakery, built its ordering app in a weekend with AI.
Product manager. Has never written a for loop and never will.
Student. Lovable, Cursor and a lot of coffee.
Marketer who got tired of waiting for the dev team.
In the core · Prize pool
The winning team takes all of it, split evenly between its players. Every dollar below is one gold word of memory.
Hover or tap a ring to see who gave it.
The minimum is $5. Give $25 or more and you get your name, link and logo.
You are the simulator · Judges
Judges open both apps, vote for the one they’d rather use and leave a line of feedback. 59 judges have points so far.
Real feedback · judges left these
“Judges every round on the bus home.”
Two minutes a round. Free to join.
Write your warrior · Pick your side
Some coding contests ask you not to use AI. We gave it a team.
Stone · precise, placed by hand
You write every line yourself. Same brief, seven days, and the diff is all yours.
Join the DevsApplications are open for next season.
Paper · copies itself everywhere
You describe the app and AI writes it. Same brief, seven days, and it keeps coming back.
Join the Vibe CodersApplications are open for next season.
Open both, vote for one, leave a line. Two minutes, free, and you earn points.
Your warrior card
Your handle seeds a tiny battle, so the core pattern on your card is yours alone. Change the handle and watch it rewrite itself.