Why a Spotify Wrapped for developers actually makes sense

Wrapped works because it is specific

Every December, Spotify Wrapped goes viral. People share their top artist, their listening minutes, the genre they did not realize they were obsessed with. The format is now copied by almost every consumer app with usage data.

It works because the numbers are specific to you and surprising. Average listener stats are not interesting. Your specific listener stats are. Wrapped is not a dashboard, it is a personal anecdote with a chart.

Developers have the same raw material

GitHub already counts everything. Every commit, every PR, every issue, every review, every day you showed up. The data is right there, broken out by day for the calendar, and most people never look at it once it scrolls off the year.

A developer Wrapped lets you actually see your year. The 12 day streak in March when you were heads down on the side project. The 32 commits in one Tuesday that wiped out a deadline. The day you switched from JavaScript to TypeScript and never went back.

What is new in 2026

Spotify cannot tell you how much of your listening was actually you choosing music versus the algorithm choosing for you. GitHub Wrapped can tell you how much of your committing was actually you typing versus an agent typing for you. That number is the closest thing developers have to the "your top artist was an AI" equivalent.

For some people that number will be 5 percent. For others it will be 60. Both are now common and neither is wrong. The interesting thing is knowing.

How to share without bragging

Three things make these cards feel okay to post:

1. Specifics, not totals. "12 day streak" reads as a story. "1,247 commits" reads as a flex. 2. A real failure or surprise. The busiest day usually involves a fire. Owning that is more relatable than the number itself. 3. The agent column. Showing the split publicly is the new normal. The people who hide it are the ones who look weird in two years.

That is the bet behind this whole project.