Senior Dev vs Junior Dev: An Honest Comparison (With Memes)
The senior vs junior dynamic is rich with comedy and genuine learning. Here's an honest (and humorous) breakdown.
The Code Review Spectrum
Junior dev submits a PR:
- 47 files changed
- 3 unrelated bug fixes included
- No tests
console.log statements throughout- Commit message: "various fixes"
Senior dev's review:
- "Please split this into focused PRs"
- "Add tests before I can approve"
- "What is this console.log doing here?"
- "Can we reuse the existing
formatDate utility?"
- 3 hours of review comments
Junior dev's response:
"I'll fix it" → Addresses 2 of 15 comments → Marks as resolved
How They Debug
Junior dev:
- Google the exact error message
- Find a Stack Overflow answer from 2013
- Copy-paste the code
- It doesn't work
- Try 6 more Stack Overflow answers
- Ask a senior dev 3 hours later
Senior dev:
- Read the error message carefully
- Add
console.log 3 levels up to find where it breaks
- "Oh, this is the same issue as that AWS thing in 2019"
- Fix it in 8 minutes
- Write a comment explaining why
The Estimation Game
Junior: "This will take 2 days"
Reality: 2 weeks
Senior: "This will take 2 weeks"
Reality: 3 weeks (they knew about the hidden complexity)
The senior estimate is still wrong, just more interestingly wrong.
The Meeting Dynamic
Junior: Silent. Takes notes. Nods. Doesn't understand half of it.
Senior: Asks "why are we doing this?" 3 times. Gets everyone back on topic. Identifies the decision that wasn't getting made.
What Junior Devs Don't Know They Don't Know
- The codebase has a 10-year-old component nobody touches because touching it breaks everything
- That regex was written by someone who left in 2021 and nobody understands it
- The "temporary" hack in deployment from 2020 is load-bearing
- The real reason they're rebuilding the auth system
The Truth
Senior devs aren't smarter. They've just been wrong more times and remember what they learned from it.
Every senior dev was once a junior dev pushing to main. Some of us still do. 🙃
