> This is great advice to become a pain in the ass that managers know they need to keep on a short leash.

If abused.

I've used this a few times for things that are in my remit, or very close to, that need doing or there will may well be more problems down the line for me or the local team more generally. If there isn't a particular problem with the intended action, I'm removing the need for someone else to make a proper positive decision. It is particularly useful when things are getting delayed by too many cooks trying to season the broth, or when it is going to require out-of-hours work and I want to push things towards a timeframe convenient for me.

Of course there are some large caveats:

* You need to be trusted, i.e. have a record of doing things both right and well, being appropriately careful with back-out plans and such, and if there have ever been mistakes on your part you need to have owned and rectified them quickly. It isn't going to fly if you are new or otherwise unknown, etc.

* You have to be complete but concise in the description of what you are doing, including what your “oh, fuck” roll-back plans are.

* You have to include everyone relevant in the announcement of your planned action, and send the notification at a time when they are likely to read it before you do the do. If there is someone key missing and others notice they will stop you, and if they don't notice and something goes wrong you have lost your trusted status for quite some time for being deceptive.

* Be prepared to be told no. Check just before the appointed time, and delay yourself a little and check again in case of a last minute “shit, no, don't do that” if someone spots a problem with the plan a little late.

* You need to trust the others around you to speak up if there is a problem, though getting negative decision can be a lot easier than getting a positive one so this isn't the most important part of this point. The most important part is you need to trust them to speak up and not enjoy watching you make a mess so they can hang you out later :)

Though having been taken over by a larger company this year, I don't think I'll ever do this again because the layers of bullshit are just too vast for it to be a safe tactic. Younger me might still have taken the chance, but I have a healthier level of not giving a shit these days - instead of “I'm doing X at time Y unless you say no” because “I really should do X at time Y otherwise problems A, B & C will arise” and if I don't get the go-ahead and problems do arise I'm the one enjoying schadenfreude⁰ and demanding overtime rates if they want me to work extra to deal with issues due to not doing the thing.

--------

[0] I know this is a slightly unhealthy attitude, and this is one of the reasons that I'm increasingly thinking that I need a significant career change¹.

[1] the main two reasons being not being happy working remote², it isn't good for my mental health, and not caring to engage with A-bleedin'-I, two massive things that increasingly mark me as not fitting in with the dev industry.

[2] I know I'm fairly unusual here and it seems to work better for many (most?) people, no need to take this as an insult to those of you gleefully working on remote teams or wanting to and jealous of those that can!