For the last two months, I’ve been showing up to open source every single day.
Not because I’m an expert.
Not because I already know everything.
And definitely not because every contribution is impressive.
I started this challenge on April 1st with one simple rule:
Contribute to open source every day for 1 year
That's it.
Some days it’s a pull request.
Some days it’s documentation.
Some days it’s reviewing code, helping discussions, fixing typos, testing things, or simply learning a codebase deeply enough to leave a useful comment.
The goal isn’t perfection.
The goal is consistency.
Why I Started This Challenge
I’m a self-taught developer learning AI, engineering, and open source through real-world building and collaboration.
Over time, I noticed a pattern in how I approached open source and contributing. Even after using GitHub for around five years, I still had what I can only describe as “git anxiety” — hesitation around commits, branches, and contributing in unfamiliar repositories. Not because I didn’t understand the tools, but because I hadn’t built enough repetition for them to feel natural.
My contribution history also reflected that. For years, it was inconsistent — periods of activity followed by long gaps. That stop-and-go pattern made it harder to build confidence, momentum, or a real sense of progress.
At the same time, I had a clear long-term goal:
getting involved in a major open source project.
To get there, I realized I needed more than just technical knowledge. I needed comfort with the workflow itself — Git, collaboration patterns, reviews, and the daily rhythm of real projects.
I also noticed something more general about how people approach open source, myself included: there’s often a belief that we need to “be ready first” before contributing.
- "I need to become better first."
- "I need to understand the entire codebase."
- "I need to build something significant before I start."
But open source rarely works like that.
The people who grow in these spaces are usually the ones who stay present — consistently showing up, even in small ways.
So instead of waiting for a perfect moment or chasing large contributions immediately, I decided to shift my focus entirely toward building a habit:
show up daily, contribute publicly, and learn in the open.
I want to paint my contribution graph into all green this year...
What Counts as a Contribution?
A contribution doesn’t always mean shipping a major feature.
For this challenge, I define contribution broadly:
- Writing or improving documentation
- Reviewing pull requests
- Opening issues
- Participating in discussions
- Reproducing bugs
- Improving examples
- Learning and documenting insights publicly
- Working on my own repositories
- Supporting community conversations
Even small actions help projects move forward.
And honestly, smaller contributions are often the best way to start.
My Daily System
I keep the process intentionally simple.
Usually it looks like this:
- Open GitHub
- Continue previous work or find one thing to improve
- Spend 30–60 minutes contributing
- Log the progress publicly
That’s all.
The simplicity matters because I want this challenge to survive busy days, low-energy days, and difficult weeks.
Consistency beats intensity.
What I’ve Been Doing So Far
Over the past two months, my days have included things like:
- contributing to open source repositories
- improving documentation and learning materials
- exploring AI agent frameworks and tooling
- building my own projects publicly
- learning collaboration workflows through GitHub
A lot of the work is small.
Some of it is invisible.
But all of it compounds.
And that’s the point.
The Bigger Goal
This challenge isn’t only about GitHub streaks.
It’s about becoming the kind of engineer who can contribute meaningfully over the long term.
Right now, I’m still exploring different projects and communities.
Over time, I want to deepen my involvement, contribute more substantially, and eventually become a trusted contributor within projects I care about.
Not overnight.
One step at a time.
What I’ll Share Here
I’ll be documenting this journey regularly on dev.to throughout the year.
That includes:
- Lessons from open source contributions
- Things I learned while building AI and developer tools
- mistakes and challenges
- contribution workflows
- beginner-friendly insights
- thoughts about consistency, learning, and engineering growth
I want this series to be honest and practical — not just highlight reels.
If You’ve Been Hesitating to Start
You do not need to be an expert to contribute.
You only need to begin.
Open source can feel intimidating at first:
large repositories, unfamiliar workflows, experienced maintainers, complex codebases.
But contribution is a skill like anything else.
You improve by participating.
Even one thoughtful comment or documentation fix matters.
Join Me
If you’re also learning in public, contributing to open source, or trying to build consistency as a developer, feel free to join me.
Start small.
Show up consistently.
Document the journey.