December 7, 2025

Cookie-crunch meets code-crunch

Show HN: Spotify Wrapped but for LeetCode

LeetCode gets a ‘Wrapped’—newbies cheer, veterans roll eyes, privacy sirens blare

TLDR: A developer launched a “Spotify Wrapped” for LeetCode stats. Commenters are split: some say LeetCode already offers Rewind, others question year‑round grinding, and many balk at the app’s ask for a login cookie—making this a flashpoint for interview culture vs privacy worries.

Someone just brought Spotify Wrapped energy to LeetCode—the website where people practice puzzle-like coding questions for job interviews—and the internet is divided. The indie project, leetcodewrapped.com, promises shareable slides of your ‘grind’ stats. But the top comment asks, “Do people use LeetCode all year round?” The vibe: newbies and job-hunters are excited to flex, while veterans roll their eyes and ask if anyone still lives in interview-prep mode.

Then came the plot twist: LeetCode already does this with its official Rewind. One side cheers the DIY lifetime recap; the other says it’s reinventing a feature that will drop again later this year. Drama level: medium-high with a sprinkle of “build it anyway” energy.

Privacy alarms? Oh, they screamed. To get deeper stats, the app hints at pasting your LeetCode login cookie—a red flag for many. The creator admits trust is thin and teases a Chrome extension if the repo gets stars, while analytics via Firebase and PostHog raise eyebrows. Meanwhile, meme-makers went wild: “Top artist: Binary Search,” “Most played: Dynamic Programming tears,” and “Minutes listened: 10k, all at 2am.” Whether you’re proud of your grind or burnt out by it, this Wrapped is giving the coding crowd something to argue—and laugh—about.

Key Points

  • A web app provides a “Spotify Wrapped”-style recap of users’ LeetCode activity and is deployed at leetcodewrapped.com.
  • The project includes setup instructions: npm install, npm run start for local, and npm run build for production.
  • Frontend uses React, Vite, and Framer Motion; backend uses Cloudflare Pages Functions (proxy) and Firebase (database & auth).
  • Analytics are handled by PostHog; Firebase Firestore and an email trigger extension support email sending, but the app can run locally without these.
  • LeetCode’s GraphQL API limits unauthenticated data to 20 recent submissions; users can supply a LEETCODE_SESSION cookie or use the calendar endpoint for full-year data.

Hottest takes

"Do people use LeetCode all year round?" — embedding-shape
"Leetcode already has a feature like this" — naet
Made with <3 by @siedrix and @shesho from CDMX. Powered by Forge&Hive.