Hacker News Reader

Comment by OtomotO | Hacker News Reader

Exactly that.

I wasn't reachable by phone for company related stuff outside my regular working hours unless I had on-call-duty, which means it was working hours.

I don't get why people would be proud about not setting boundaries.

View on HN

It really depends on where you want to steer your career. There's some roles, especially in management, where "working hours only" isn't really an option; if you aspire to one of those you've gotta convince people you'll do what's necessary.

Some people are in it for the challenge. Someone else's outage? Yeah I'll happily help diagnose it, analysing and figuring out where the issue is can teach you a lot of things.

For the record, this was never at night. Late in the evening, sure.

Also sometimes (depending on the company) being seen to visibly chip in fighting fires can win you real credibility that you can put in the bank and then use later when you want to slightly slack off for a bit.

So it can actually make logical sense to do it occasionally even from a purely selfish perspective if it's half an hour on a random Tuesday evening and you aren't actually doing anything else important.

All depends if the company is actually going to be grateful or not though

Keep your ops people happy. Help them when you can, it's the fairest way i would say to not have to be on call. It also makes them feel like they're not on their own. You're all on the same team.

Not sure if upper management sees this stuff. For the number of times I've fixed other people's crap (or found the root cause, so they can just fix it) I don't think I got any recognition for that.

This is relatable. Though I’d add that the company can’t be grateful, it’s just a machine. But the colleagues you’re helping out, they absolutely can be grateful, and will sing your praises, leading to positive things happening. In the right type of company.

I do that as well, since I am my own business

Reply on news.ycombinator.com