Every developer's GitHub contribution graph tells a story. Not the story GitHub thinks it's telling - not "this person made 4 contributions on a Tuesday" - but a deeper one. A story about rhythm, obsession, rest, and reinvention.
We've rendered thousands of these graphs as star atlases since launching Codex Stellarum, and patterns have emerged. Not patterns in the data - patterns in the lives behind the data.
Here are the ones we see most often.
The Steady Orbit
Some developers have contribution graphs that look like a heartbeat - consistent, rhythmic, unbroken. Day after day, week after week, the same steady pulse of commits. These aren't necessarily the most prolific contributors. They're the most disciplined.
On a star atlas, the Steady Orbit looks like a continuous band of evenly-spaced stars. No dramatic flares, no dark gaps. Just light, all the way through. It's the kind of pattern you see from senior engineers who've been at the same company for years, or from open-source maintainers who treat their project like a garden - tending it daily.
There's something deeply beautiful about consistency. In a world that celebrates launches and breakthroughs, the Steady Orbit is a quiet monument to showing up.
The Supernova
Then there's the opposite: long stretches of near-silence, punctuated by explosive bursts of activity. Weeks of nothing, then suddenly 40 commits in a day. Then silence again.
The Supernova pattern shows up as dramatic clusters of bright stars surrounded by dark void. It's visually stunning - the contrast makes the active periods burn even brighter.
This is the pattern of builders. People who get seized by an idea and disappear into it for a week. Hackathon winners. Weekend project addicts. Founders in the early days of a startup, writing code like their life depends on it - because for a while, it does.
The gaps aren't laziness. They're recharging. The Supernova needs darkness to burn.
The Renaissance
This one is the most fascinating pattern of 2025 and 2026 - a graph that was nearly dark for years, then suddenly ignites.
The most dramatic example might be Shopify CEO Tobias Lütke. His GitHub profile tells the story in three numbers: 94 contributions in all of 2024. Then 833 in 2025. Then 957 in just the first 45 days of 2026. A near-vertical spike after almost a decade of near-silence.
Lütke built the original Shopify codebase himself in 2004 using Ruby on Rails. Then he did what every founder-CEO does - drifted into meetings, board decks, and strategy. The thing that made him dangerous collected dust for twenty years. Until AI coding tools brought him back. In March 2026, he used an AI agent to run 120 automated experiments on Shopify's Liquid template engine, landing a pull request that made it 53% faster. The CEO hadn't just returned to the codebase - he was shipping performance improvements to production.
He's not alone. Coinbase CEO Brian Armstrong posted his own GitHub graph on X in February 2026 with the caption: "Beware, it's 2026 and the CEO is back in the code base thanks to AI." Y Combinator CEO Garry Tan has been open about staying up until 5am building with Claude Code - then publicly revealing that 25% of YC's Winter 2025 batch had codebases that were 95% AI-generated.
On a star atlas, the Renaissance is the most hopeful pattern there is. Darkness giving way to light. A sky that was nearly black, filling with stars. It proves that chapters end, but the book doesn't.
And the current chapter being written across the industry is remarkable: the people who stopped coding a decade ago are building again. Not because they have to. Because the tools finally let them.
The Fade
This one is bittersweet. A graph that starts dense and bright, then gradually thins out. The stars get fainter. The gaps get wider. The trail ends.
The Fade can mean many things. A developer who moved into management and stopped writing code. Someone who burned out and stepped away. A person who found a different passion. Or simply someone whose work moved to a private repository that GitHub's public graph can't see.
On a star atlas, the Fade looks like a comet trail - bright at the head, dissolving into darkness. It's one of the most poignant patterns we see, because it reminds you that every graph is a snapshot of a specific chapter, not the whole book.
The Seasons
Some graphs have a clear cyclical rhythm. Active in winter, quiet in summer. Or the reverse - alive during conference season, dormant in December. You can see holidays, academic semesters, fiscal quarters.
The Seasons pattern is particularly visible on the Planisphere layout, where months orbit the circumference like hours on a clock. The seasonal rhythm becomes literal - you can see which months of the year this person writes the most code, year after year.
It's a reminder that developers are human. We have rhythms. We're affected by weather, holidays, deadlines, and the simple fact that sometimes you need to close the laptop and go outside.
The Constellation
Finally, there's the pattern that defies categorisation. A graph so unique, so idiosyncratic, that it doesn't fit any archetype. Dense clusters here, scattered points there, a strange gap in the middle, an unexpected burst at the end.
Every atlas is a Constellation, really. The archetypes above are just lenses - ways of reading a pattern that is, ultimately, as unique as a fingerprint. No two developers have the same graph. No two have the same story.
That's the whole point of Codex Stellarum. We don't think your contribution history should be reduced to a number or a colour-coded grid. We think it should be art. Because the shape of your code is the shape of a chapter of your life, and that deserves to be beautiful.
Want to see the shape of your code? Enter your GitHub username on our homepage and preview your atlas for free.