"How do you make money from this?"
Every builder hears it. From a friend over coffee. From a relative who means well. From a stranger in the comments. The question arrives early, and it arrives sure of itself.
Underneath it is an assumption: a thing worth building is a thing that earns. Revenue is the proof. No revenue, no point.
For a lot of solo work, that misses what the project is for.
Some projects exist to learn a thing the day job never touched. Some exist to prove the builder still can. Some scratch an itch nobody else was scratching. Some keep the craft sharp between paychecks. None of those show up on a balance sheet. All of them paid for themselves.
The question treats every repo like a startup. Most repos aren't startups. They're the gym. Nobody asks what you earn from lifting.
But the honest version is harder.
Sometimes the money question is the one true thing in the room. The project that should charge and never did. The free tool quietly carrying a hosting bill every month. The hobby that stopped being a hobby and became unpaid work with users who file bugs.
When a project demands the hours of a job and returns the income of a hobby, "how do you make money from this" stops being naive. It becomes the question that got avoided for a year.
The skill isn't having an answer. It's knowing which projects owe one.
Some things are built to earn.
Most things are built to learn.
The trouble starts when you can't tell which one you're holding.