How we built paint.wtf, an AI game with 150k submissions that judges your art
In this technical retrospective (2021), @rocauc shares practical architectural lessons learned from running, scaling, or migrating production software under lean constraints.
Core Principles for Independent Builders:
Defaulting to simpler architectures (such as monolithic frameworks, SQLite, or managed VPS) prevents early engineering bankruptcy.
Evaluating true compute and egress costs reveals that high cloud bills can often be slashed by 80%+ through judicious re-platforming.
Code you write at 2 AM as a solo engineer must be easy to debug six months later without complex microservice dependencies.
Community Debate Themes:
HN engineers debated the tradeoffs between cloud convenience and raw server economics, database indexing strategies, and resisting premature architectural complexity.
CATEGORY Frugal Engineering →
HISTORICAL ERA Pandemic Bubble (2020–2022)
COMMUNITY SCORE ★ 6 points
TOTAL DISCUSSIONS 3 comments
This game is so fun. My girlfriend and I play it pretty much every night. Sometimes the outcomes are kind of wacky - I've gotten last place with what I think is museum-quality art (well, at least my mom would like it) - but it's consistently hilarious
love paint!! and Joseph from roboflow was super helpful in helping me understand the game and use the AI the way they did.
This one lit up over the course of a weekend. Hilarious game.