The Unspoken Etiquette of Following Back on GitHub
Somewhere in GitHub's culture there is an unofficial contract nobody writes down. You follow a developer whose code you admire; they feel a mild obligation to look at you back; and within days, a mutual follow exists. It is not merchandise, and it is not meaningless — but like all social contracts, it can be performed badly. Follow and follow back without judgment, and your feed becomes noise and your network becomes trivia. Do it with intent, and mutual follows become the quiet backbone of a credible developer presence. This is the etiquette that sits between.
Follow Because the Signal Is Worth It
GitHub follows serve a real purpose: they subscribe you to a developer's star events, release activity, and public achievements. That is a signal stream worth curating. Every follow answers the question "whose actions do I want to know about?" The best follow decisions are therefore picky. Follow repositories and people whose trajectory you want to ride — maintainers of tools you use, people who solve problems you care about, accounts whose next repo might be your next dependency.
This is why spamming follows at strangers fails twice: it pollutes your own signal, and it visibly pollutes the recipient's follower count with accounts that follow everyone. Neither side gains anything except a number that smart watchers discount.
The Follow-Back Bond, Done Consciously
When someone follows you, you are under no technical obligation to reciprocate — and the etiquette is not "everyone gets a return follow." It is subtler:
- Follow back the people who actually engage. A developer who stars your repos, comments on issues, or contributes is showing genuine interest. That is a relationship, not a transaction. Return the follow and it becomes physical.
- Follow back real peers, even if they are early. A junior developer with one interesting repo is a better follow than a celebrity account that never appears. Both are real; one is a community.
- Do not punish mutual-follow systems. Understand that automated exchange networks like follo exist because follow-backs are asynchronous — you follow eleven, you receive ten, and at any moment a developer you followed is still deciding about you. That is not spam; it is the internet's slow handshake.
What an Exchange Deals In
Which brings us to the honest mechanics of follo's free tier: 11 out = 10 in. Follow eleven developers, and ten real developers (or their queue positions) follow you back. The service's entire value is solving the coordination problem — half the people you would want to follow-back never find your profile, so the network surfaces you to each other — while enforcing a real-accounts policy that keeps the exchange from becoming bot theater.
The etiquette boundary is simple: use networks to solve the discovery problem, not the quality problem. A follow-back hook gets your profile seen; what it is seen for is still 100% your README, your repos, and your history.
When NOT to Follow Back
Equally important is the list of accounts you should pass on — not out of snobbery, but because a follower list is part of your own signal, and junk follows drag it down:
- Empty shells. No repos, no contributions, no bio, starved-looking — follows from these add noise and nothing else.
- Mass-following bots. An account following 5,000 people that follows back 10 is a collector, not a developer. Their follow is anticipation, not interest.
- Impersonation and spam accounts. Brand-new names riding a famous handle, or accounts whose only activity is "check this link." Follow-back here endorses a scam.
- Anyone whose content would embarrass you on your profile. Follower lists are public. You own what you display.
The Healthy Network Shape
A credible following ratio looks less like a pyramid and more like a conversation — people you follow, people who follow you, and a healthy overlap where both are true. If your account follows 10 and has 400 followers, you look like a hoarder of attention. If you follow 400 and have 10, you look like a collector of hollow numbers. The middle ground, shaped by picky follows and genuine reciprocation, reads as a person in a community rather than a node in a market.
Frequently Asked Questions
Q: Should I follow back every real developer who follows me?
A: Yes, as a default — with the exceptions above as the guardrails. Real developers who found you are the community you actually want, and every one of them adds to a profile that reads as "active and generous, not transactional."
Q: Does the 11-out-for-10-in exchange violate follow etiquette?
A: It codifies it. The exchange does in minutes what the natural follow-back loop does in weeks, with real accounts and no fakery. What it does not do is manufacture quality — a developer still decides whether to keep following based on your content. The etiquette-first crowd should read how discovery actually works.
Q: Is it rude to unfollow someone later?
A: Unfollowing is normal hygiene. If a developer's signal becomes noise, or an account goes dormant or botty, prune it with the same judgment you used to follow. Nobody owns your following list.
Q: What is the single most underrated follow etiquette move?
A: Following niche developers whose projects are small but sharp. It costs nothing, it signals genuine taste on your profile, and a thoughtful follow from a real peer is exactly the kind of attention small developers remember and reciprocate.
Follow Like a Human Being
The etiquette has one rule underneath everything: follow like you are joining a community, not harvesting leads. Be picky about your inbound signal, reciprocate generously with real peers, prune the junk, and let honest networks — including follo's 11-for-10 exchange — solve the discovery problem without turning you into a bot. Your profile will read as a person, your feed will stay useful, and your follower count will mean something at a glance. Start following with intent on follo today.