For years we were told that building publicly was the best way to grow as a developer. “Share your code”, “document your process”, “make constant commits”. And yes… all of that works. Until he stops doing it.
Hoy, tu historial en GitHub no solo muestra lo que sabes hacer. It also shows who you were, what you thought and what you believed in… and that can work against you.
Web: https://gitgost.leapcell.app
Repo: https://github.com/livrasand/gitGost
The uncomfortable side of commits
Every commit you make tells a story. Not only technical, but personal.
Recruiters and companies no longer limit themselves to seeing your CV. They review:
- What projects have you touched
- How you write your commit messages
- What technical decisions did you make
- How you interact in issues and pull requests
This may seem fair… until it isn't.
Because that context is almost never complete. A commit does not explain:
*if you were learning
*if it was an experiment
*if it was a temporary bad decision
*or if you simply changed your mind later
However, it remains there. Permanent.
Your opinions are also recorded
GitHub is not just code. It's discussion.
Every comment on an issue, every technical debate, every position on architecture... everything is associated with your identity.
And here the problem begins.
Technical opinions evolve. What you defended 2 years ago may seem like a mistake to you today. But on GitHub there is no “emotional context” or “personal evolution.” There are only records.
Even worse:
- You may be perceived as conflictive due to a specific debate
- As inexperienced by old decisions
- Or as rigid for defending something you no longer think about
Your history does not distinguish between growth and contradiction. It only shows traces.
Contribute to the “wrong”
Open source has an idealistic narrative… but the reality is more complex.
What happens if you contribute to:
- a project with a controversial philosophy?
- a tool that later becomes controversial?
- a repository associated with questionable decisions?
Even if your contribution has been technical, neutral or even minimal... your name remains there.
And someone, at some point, can interpret that without context.
It doesn't matter if it was years ago. It doesn't matter if you no longer agree.
It's in your history.
The permanent digital identity
This is where everything converges.
Your GitHub profile becomes a kind of “permanent digital identity”:
*Does not expire
- Does not restart *Does not forget
Unlike real life, where you can change, learn and redefine yourself... on the internet everything is indexed, accessible and evaluable.
And that creates a real tension:
*Build in public or protect your privacy?
- Be transparent or be cautious?
- Experiment freely or take care of your reputation?
So... do we stop contributing?
Not necessarily.
But it is worth questioning the idea that everything must be done publicly and permanently.
There is space for:
- experiment without pressure *contribute without full exposure
- explore ideas without them defining your long-term identity
In this context, different approaches are beginning to emerge. Tools that allow the contribution to be separated from the personal trace, or at least give the developer more control over what is associated with their identity.
It's not about hiding bad intentions.
It is about recovering something basic: the right to evolve without your technical past haunting you forever.
An uncomfortable reflection
Quizá la pregunta no es si debes construir en público.
Otherwise:
how much of yourself are you willing to leave permanently recorded?
Because in the end, not everything you create today represents who you will be tomorrow.
Top comments (0)