alt Hacker NewsTaking it at face value makes it good advice and interpreting it as CYA hedging makes it bad advice. My bet is the author intended the good advice they actually said rather than the bad faith guess to what they meant that makes it bad advice.
And there are plenty of things that are your job, but you would like the boss in the loop on without actually making it their job.
You say if it's your job then do it, and that's roughly what the advice given here is. The only place you're in disagreement is that you don't see any room for nuance when something is your job but worth notifying the boss about in advance.
> The only place you're in disagreement is that you don't see any room for nuance when something is your job but worth notifying the boss about in advance.
You read a different article.
FTA:
> ”Hey, boss, I am going to install action X, which should solve the XYZ problems we’ve been having. Will take care of this on Monday unless I hear differently from you.”
The parent's point is that lighting a fuse and saying you'll do something when the fuse runs out regardless of the boss' approval in a situation where you want to run something by them...is career suicide.
FTA:
> When you have something you want to do and that you feel is in scope for your position, but you want a bit of reassurance or to let the boss know what you are up to, it’s common to reach out and ask them for permission. Don’t. Don’t ask for a yes. Instead, offer a chance to say no, but with a deadline.
The qualifiers of "needing reassurance" and "asking for permission" combined with a notification on a fuse is way different framing than "notifying the boss about it in advance."