Bound to Main

Every few days, someone asks me what they should build. They want to get into open source. They want to grow. But they are waiting for me to hand them the idea. They want a ticket. They want an assignment. They want permission.

I understand the reflex. In school, they teach you to wait for the syllabus. In corporate life, they teach you to wait for the sprint ticket. After enough years, you start to believe that every important idea must come from someone above you. You forget that the terminal is yours to control. You forget that you can start something without a manager's approval.

I have felt this myself. Early in my career, I would stare at a blank editor and wait for someone to tell me what to write. I have watched senior engineers with impressive titles sit in meetings for hours, debating whether a junior's proposal is worth trying. I have seen lead developers freeze when an architect enters the room, suddenly unsure of calls they made confidently just moments before. It is not a skill problem. It is a habit. We have been trained to treat our own ideas as read-only.

Psychologists call this learned helplessness. It happens when you stop believing your actions matter. But here is what I have learned. The feeling is real, but the cage is not. You can step out of it anytime. You just need a place where nobody owns the roadmap but you.

The open source ecosystem is that place. Nobody assigns you a ticket. Nobody validates your idea before you start. You either spot a problem and fix it, or you do not. The codebase does not care about your title. It does not care about your salary band or your vesting schedule. It only cares about the quality of the work and the clarity of the communication.

I found this out by accident. I was using a tool in my own workflow. I forked the repository, ran it locally, and kept using it every day. After a few days, I noticed a small gap. A missing validation. A confusing error message. Nothing dramatic. I fixed it. I wrote a test. I opened a pull request. There was no standup meeting. There was no approval process. It was just me, my editor, and a problem I chose to solve. When the maintainer merged it, I felt something I had not felt in years. I felt like my judgment still worked. It was a tiny commit. Maybe twelve lines of code. But it was mine. I owned it from start to finish.

That is the real reason to contribute to open source. It is not about becoming a world-famous maintainer. It is not about adding a line to your resume. It is about proving to yourself that you can still build without permission. You can still read code, spot a flaw, and ship a fix. You can still own the outcome.

Every time you submit a patch, you are voting with your actions. You are saying that you still trust your eyes and your hands. This is a fundamental skill. AI tools are powerful. They can speed you up. But they cannot teach you how to trust your own taste. That comes from doing the work yourself.

If you do not know where to start, stop looking for the perfect idea. The perfect idea is a trap. It is just learned helplessness wearing a clever disguise. There is no perfect idea. There is only the repository you have not forked yet, and the branch you have not created.

Find a tool you already use. Clone it. Run it on your machine. Use it. Break it. Fix it. You do not need a grand vision. You do not need a perfect idea. You just need to create a branch that belongs to you. Because the only way to remember that you know how to build is to build. And you never really forgot. You just stopped practicing.