The Senior Developer's Lament: From Coder to Critic
Description
A two-panel meme that captures a common career transition for software engineers. The top panel shows a GitHub-style contribution graph heavily skewed towards code reviews. The four axes of the graph are 'Commits' (14%), 'Pull requests' (14%), 'Issues' (0%), and 'Code review', which dominates at 72%. The bottom panel features a dramatic, close-up screenshot of a grimacing Kratos from the 'God of War' video game series, with the subtitle, 'By the gods, what have I become?'. The humor arises from the juxtaposition of the mundane reality of a senior developer's workload with Kratos's epic despair. It perfectly illustrates the moment a developer realizes their role has shifted from being a primary code contributor to spending the majority of their time reviewing others' work, a common and often bittersweet milestone in a technical career path
Comments
10Comment deleted
I've traded my IDE for the PR queue. My new job is basically being a very expensive, opinionated linter
GitHub says 72 % of my contributions are code reviews - turns out I’ve been silently refactored into a human circuit breaker between prod and anyone who still thinks ++ is atomic
The moment you realize your GitHub graph perfectly illustrates Conway's Law in reverse - instead of shipping org charts, you've become the org chart, spending 72% of your time gatekeeping other people's code while your own PRs gather dust in the 14% graveyard
The inevitable transformation from 'I ship features' to 'I ship approvals' - where your GitHub contribution graph becomes less a testament to your code and more a monument to your ability to diplomatically suggest 'maybe we should extract that into a function.' You've ascended from writing `git commit` to writing `git comment`, and your PRs now have more reviews given than received. The staff engineer's curse: you've become the bottleneck you once complained about, except now you understand *why* that 500-line PR touching 47 files really does need another round of review
Commits at 14%, but I've optimized more bad code than Dijkstra's shortest path - senior dev singularity achieved
When the dashboard says 72% code review, you’ve become a distributed semaphore throttling throughput - an SLO for commits with “nit: naming” as your write path
72% code review, 14% commits - I’m a human two-phase commit now: PREPARE = “LGTM”, COMMIT = “Merge”
He became a boss Comment deleted
Teamlead Comment deleted
He becomes a code reviewer,duh Comment deleted