lulzx.comEverything good in my career came from a side project.
My first job came from a Telegram bot I built for fun. My freelance clients found me through open source repos. My best technical skills came from projects nobody asked me to build.
The bot was running. Someone could talk to it. That was enough to start a conversation that became a job. Later a stranger would clone a repo and write me. I did not send a deck. I sent a link. The link had to do the talking while I was asleep.
You pick the walls
Side projects have one advantage over work projects: you choose the constraints. Want to learn Rust? Build something in Rust. Want to understand ML inference? Port a model. Nobody's telling you to use the company's approved stack. The ticket at work is whoever shouted last. The night project can be the one question I cannot stop turning over.
That freedom is also the trap. A folder of half clones teaches you how to start. A bot that still answers, a CLI someone else can install, a model that runs on the machine on my desk. Those have a stop condition. They work, or they don't. I can feel the gap. I go read the one page I need. I change the code. I run it again. The skill sticks because the project punishes the wrong answer.
Unasked work is where I get to be wrong in private and still keep the lesson. Work will not let me throw away the stack for a month to see if the types pay off. A weekend CLI will.
What people are actually hiring
I don't build side projects to "build a portfolio." I build them because I'm curious about something and the only way to understand it is to build it. The portfolio is a side effect. A hiring manager, or a client, is looking for evidence that I finish things when nobody files a ticket. The public repo is that evidence if it still builds. A graveyard of tutorials is evidence of the opposite.
I keep the ones I still want to open. I delete or archive the rest. The first job and the freelance work both came from a project that had users, even if the users were me and a handful of strangers. Curiosity picked the problem. Shipping it made it visible. Visible and finished is what turned into money. A private experiment can teach you. A public one can also hire you. The next one starts the same way. I want to know how something works, so I build a small version that has to survive contact with a real input.