Elementary

45 Days Straight: One Person's Game Marathon

pzxc's "Show HN" streak on Hacker News hit day 45 — one playable browser game shipped every single day, built with AI-assisted vibe-coding. From Gravity Lander to Pipes to today's Elementary, the genre range is wild, but every title shares the same DNA: minimal rules, solo-dev feasible. This isn't a funded studio's output. It's one person's daily commitment, like a coding Ironman triathlon. The HN post got exactly 1 point and 0 comments — painfully cold. But that's the reality of indie dev: most people won't notice you, and you ship anyway.

What Elementary Actually Plays Like

One sentence: a random element lights up on the periodic table, you pick its name from four choices before the timer runs out. Correct answers add points, wrong ones subtract, time's up means game over. Sounds like a 2010 Flash game, but the leaderboard tells a different story — clay.walson hit 16,300 points, Pinkspoonbill scored 5,810. People are actually grinding this, trying to memorize where obscure elements sit. The gameplay isn't carried by graphics or narrative; it's the oldest loop in game design: timed competition. The four-choice format is also smart — options are confusing enough to be challenging but logical enough to feel learnable.

Why Daily Ship Is Harder Than a Big Project

The most common way indie devs die: project gets too big, they quit halfway. pzxc's strategy is the opposite — one tiny game per day, but it must ship. The upside is obvious: you never sink into perfectionism because there's simply no time. The downside is equally clear: every piece is MVP-level. Elementary's art is essentially zero (periodic table screenshot plus four buttons), sound design is unknown, and gameplay depth is about sixty seconds. But after 45 days, this is muscle memory training — you internalize the full zero-to-publish flow and execute it daily. That's more effective than any "Learn X in 30 Days" tutorial.

How Complex Can This Technically Be?

Elementary is almost certainly pure frontend — HTML + CSS + JavaScript, probably DOM manipulation rather than Canvas (a periodic table is fundamentally a grid layout, no canvas rendering needed). The countdown timer, scoring system, and leaderboard are basic Web APIs. No backend authentication (the leaderboard looks like local storage or simple cookies), no multiplayer, no complex state management. This isn't an insult to the project — quite the opposite. Under daily shipping pressure, choosing a tech stack you fully control is the only rational decision. Complexity is for when you have time to debug.

Who Should Play? Who Should Learn From This?

Elementary serves two audiences. First, chemistry beginners — use it to test your periodic table familiarity; it's marginally more engaging than flashcards. Second, indie developers, especially those who "want to build but never start." pzxc proved something over 45 days: you don't need a great idea, great art, or a great engine. You need a system that lets you ship daily. As for limitations — this is a two-minute minigame. Play it once and move on. It won't reshape your understanding of chemistry, and it won't become the next Wordle. But that was never the point.