It’s 9:47 PM.
You’re about to shut your laptop.
Then you see it…
Your manager just pushed a commit. 👀
And suddenly you’re like:
"Maybe I should stay a bit longer..."
🤔 Let’s Be Honest
Most of us have been there.
Not because the work needs it,
but because it feels expected.
That silent pressure:
- “What if they think I’m not committed?”
- “Everyone else is online… should I be too?”
- “Will this affect my growth?”
🚨 Reality Check
Your manager working late doesn’t automatically mean:
- You’re expected to do the same
- You’re falling behind
- You’re less dedicated
Different role. Different responsibilities. Different boundaries.
Sometimes they’re:
- Handling cross-team chaos
- Catching up after meetings all day
- Or just... bad at logging off 😅
🧠 What Actually Builds a Strong Dev Reputation?
Not green dots at midnight.
But things like:
- Shipping clean, reliable code
- Communicating blockers early
- Respecting deadlines (without drama)
- Being consistent — not constantly available
⚖️ The Trap of “Visible Productivity”
Being seen working ≠ being effective
Late-night work often leads to:
- Sloppy commits
- More bugs
- Slower thinking
- Next-day burnout
You’re not gaining extra points.
You’re just borrowing energy from tomorrow.
💡 A Better Approach
Next time you see that late-night activity:
👉 Pause
👉 Ask yourself: “Is this actually urgent?”
If not:
- Log off without guilt
- Pick it up fresh tomorrow
- Protect your focus (and sanity)
🚀 Final Thought
You were hired for your skills —
not your ability to stay online the longest.
Don’t turn your career into a 24/7 status indicator.
Top comments (0)