Someone made a complete 3D hockey game in 22 minutes yesterday. Multiplayer. Online. Running in a browser. No prior assets, no game engine setup, no months of development hell. Just a conversation with an AI model and 300,000 tokens later, hockey happened.
The creator went for a bike ride afterward, marveling at all the people who had no idea the world had changed. I rather suspect the world noticed about as much as it usually does when everything shifts beneath our feet. Which is to say, not at all.
We are living through the strangest revolution in human history. One where the most profound changes arrive with all the fanfare of a software update. No parades, no declarations, no dramatic music. Just someone casually mentioning they built a game faster than it takes to watch a sitcom.
The disconnect would be funny if it weren't so complete. While this person cycled through their neighborhood. Probably every house they passed contained someone struggling with Excel formulas or waiting three weeks for their nephew to fix their website. The future arrived Tuesday at 2:47 PM, and nobody sent a memo.
The Casual Apocalypse
There is something deeply unnerving about revolutionary technology that arrives with a shrug. Previous technological leaps announced themselves properly. The printing press, the steam engine, electricity, the internet. These came with obvious drama, clear before-and-after moments that even the most oblivious observer could recognize.
But AI development follows different rules. It sneaks up on you like a polite assassin. One day you are googling "how to center a div in CSS" for the thousandth time. The next, someone is casually generating entire functional games while you are still figuring out whether to use flexbox or grid.
The hockey game itself is almost beside the point. Sure, it is impressive in the way that watching someone juggle chainsaws is impressive. But the real story is not what got built. It is how it got built, how quickly. And how the person who built it seemed more surprised by everyone else's obliviousness than by their own achievement.
We have reached the point where creating software is becoming as casual as ordering takeout, and somehow this feels both inevitable and impossible at the same time.
This is what exponential change looks like from the inside. Not a smooth curve on a chart, but a series of Tuesday afternoons where someone rebuilds an entire industry between lunch and dinner. The graphs make it look elegant. But the reality feels like stumbling down stairs in the dark.
The Expertise Evaporation Event
Consider what just evaporated in those 22 minutes. Years of learning game physics. Months of mastering networking protocols. Weeks of debugging collision detection. Hours of sprite animation and sound design. Entire careers built on knowing how to make digital hockey pucks bounce properly.
Not eliminated, mind you. Evaporated. Like morning dew that simply stops existing when the sun gets serious about its job.
The traditional response to this sort of disruption involves careful analysis of which skills remain valuable and which need updating. Thoughtful retraining programs. Measured transitions. The assumption that change happens slowly enough for institutions to adapt gracefully.
But what happens when the entire concept of expertise gets compressed into a 22-minute conversation? When the gap between "I have an idea" and "I have a working product" shrinks to the length of a coffee break?
We are about to find out. And judging by how long it took the world to notice someone had just rebuilt game development from scratch. The adjustment period might be more interesting than anyone anticipated.
The Infrastructure Nobody Sees
The most remarkable part is not that this happened. And the most remarkable part is that it happened quietly, using infrastructure most people do not even know exists. No special hardware, no million-dollar development studios, no teams of specialists. Just access to a language model and enough tokens to have a productive conversation.
This is like discovering someone built a skyscraper in their backyard using only tools they ordered online. The tools existed, the knowledge existed, the capability existed. But somehow the combination felt impossible until someone actually did it.
The creator mentioned 300,000 tokens like this was a meaningful constraint. For context, that is roughly equivalent to a short novel. They traded a book's worth of computational conversation for a complete multiplayer game. The exchange rate between human ideas and digital reality just shifted dramatically, and most people missed it entirely.
Meanwhile, traditional game studios are still measuring development cycles in years. Planning release schedules around holiday seasons two years in the future. Hiring teams to work on projects that might be obsolete before they launch.
The mismatch between institutional timescales and individual capability is becoming comical. Like watching a freight train race a teleporter.
The Democratization Dilemma
Every technology follows a predictable path from exclusive to accessible. What usually takes decades happened here in months. Professional game development went from requiring specialized teams and substantial funding to needing a decent internet connection and an idea.
This should be universally celebrated. More people creating things, fewer barriers to entry, creativity unleashed from the constraints of technical expertise. The democratization of digital creation sounds like exactly the sort of progress everyone claims to want.
So why does it feel vaguely unsettling?
Perhaps because we are not quite ready for a world where the limiting factor is imagination rather than put in placeation. Where the question changes from "can this be built?" to "should this be built?" Where technical impossibility stops serving as a natural filter for bad ideas.
The future arrived Tuesday at 2:47 PM, and nobody sent a memo.
The Silence of Transformation
The cyclist's observation about people not knowing the world had changed reveals something profound about how transformation actually works. We expect revolutions to announce themselves. Trumpets, headlines, obvious disruption that nobody could miss.
Instead, we get someone casually mentioning they built a hockey game faster than most people can decide what to have for dinner. The most significant changes often arrive wearing the disguise of minor curiosities.
This quiet arrival might be the most important part. When change comes with fanfare, institutions can prepare, adapt, respond. When it arrives as a casual Tuesday afternoon achievement, the response time approaches zero. By the time anyone notices what happened, the new reality is already normal for the next generation.
The hockey game is not the story. So the hockey game is the punctuation mark at the end of a sentence nobody realized was being written. A demonstration that individual capability just leaped forward by orders of magnitude while everyone was looking elsewhere.
The Attention Arbitrage
While the world debates AI safety, AI regulation, AI ethics, and AI economics, someone quietly used AI to collapse game development into a coffee break. The gap between what people worry about and what actually happens continues to widen.
This is classic attention arbitrage. Everyone focuses on the dramatic possibilities while the mundane impossibilities become possible without anyone noticing. We spend months debating whether AI will replace programmers while someone demonstrates that programming itself just became optional for certain types of projects.
The debate continues in conference rooms and academic papers while reality quietly rearranges itself outside the window. By the time the committees reach consensus on what might happen, it already did.
The New Normal Arrives Early
In five years, this story will sound quaint. Of course you can build a multiplayer game in 22 minutes. Why would that be remarkable? The tools will be better, the process will be smoother, and the result will be more sophisticated. Today's impossibility becomes tomorrow's tutorial.
But right now, we exist in the brief window between "this cannot be done" and "obviously this can be done." The moment when magic looks like technology and technology looks like magic. When someone cycles through their neighborhood marveling at how quickly everything changed and how little anyone noticed.
The world did change yesterday. Not because someone built a hockey game, but because someone demonstrated how casually impossible things can become possible. How individual capability can leap forward without institutional permission. How the future can arrive on a Tuesday afternoon with no advance warning.
The cyclist was right to marvel. The rest of us were just looking in the wrong direction.
Filed under. things that were always going to happen. Eventually. Just not this quickly.
Go Habs Go, indeed. In a world where hockey games can be conjured from conversation, supporting your team feels both more important and more achievable than ever. After all, if someone can build the game in 22 minutes, surely the Canadiens can figure out how to win it.
I checked. They are still working on that part.
