On August 4, a Hacker News user dutifully posted the site’s monthly ritual: “Ask HN: What are you working on?” Six days later, the thread had mustered 20 upvotes and 54 comments. For a forum that can generate a thousand points for a well-timed complaint about cloud bills, that number is a rounding error. The companion thread—“Who is hiring?”—drew the usual flood of listings from startups and labs hungry for talent. The message was hard to miss: the community still cares intensely about who is paying for work. It just doesn’t care much about what anyone is building on the side.
This is not a crisis. It is a clearing.
The Side Project Was Always a Means, Not an End
For two decades, the personal project was the tech industry’s favorite origin story. Facebook began in a dorm room. Slack emerged from a failed game. Stripe’s founders built a payments API because they were annoyed by how hard it was to accept money online. The mythology was so powerful that “what are you working on?” became a shibboleth—a way to signal that you were a builder, not a cog.
But the mythology obscured an uncomfortable truth: the side project was never really about the project. It was a credentialing device. It got you into Y Combinator. It got you a job at a place that valued “initiative.” It was a lottery ticket with a very long tail. The actual software—the recipe manager, the to-do list, the test-runner tweak—was almost beside the point. What mattered was the signal it sent to investors and hiring managers.
That signal has lost its value. The market no longer needs to be convinced that someone who can ship a weekend project is worth a look. It has GitHub contribution graphs, LeetCode scores, and AI-assisted coding demos that can be generated in an afternoon. The credentialing function has been automated away, and what remains is the project itself—which, for most people, is not enough to sustain the effort.
The Interesting Problems Moved Indoors
There is a second, more structural reason the thread is quiet. The problems that once made side projects compelling have been absorbed by the companies that now employ the people who would have built them.
A decade ago, if you wanted to experiment with a new database, you spun up a VPS and wrote a blog post about it. Today, your employer is already running that database at scale, and the interesting work is not getting it to run—it’s tuning it for a workload that costs six figures a month. That work is invisible to the outside world. It doesn’t produce a Show HN post. It produces an internal design doc and a promotion packet.
I was in a Slack channel last week with a dozen engineers who, five years ago, would have spent their Saturdays shipping micro-SaaS products. I asked if anyone was building anything outside of work. The silence stretched. Finally, one of them typed: “I’m building a RAG pipeline for our legal team. It’s the most fun I’ve had in years.” Nobody argued. The side project, for this cohort, has been rehomed inside the firewall—not because they lack ambition, but because that’s where the ambition is now rewarded.
The Hobbyist Era Was a Transitional Phase
There is a temptation to mourn this shift. The “indie hacker” movement still has its evangelists, and the monthly thread will continue to attract a few dozen replies from people building recipe managers and Gleam test runners. But the era when the side project was the center of gravity for technical creativity is over, and that is not a tragedy.
It is, in fact, a sign of maturity. Industries do not stay in their garage phase forever. Automobiles were once built by hobbyists in sheds; now they are built by supply chains that span continents. The same transition has come for software. The infrastructure is too good, the incumbents too capable, and the problems too large for a weekend project to matter in the way it once did. The people who would have been the next generation of founders are now inside the machines, tuning them, and the machines are better for it.
The 20-point thread is not a failure of creativity. It is a receipt. The side project did its job—it built the industry that no longer needs it.