If you’re in some federal agency and “DOGE” comes coup-knocking on your door, and if your system is something they actually want to keep at least partially functioning — the procurement system, for example — then the single most effect thing you can to do •help the coup succeed• is to make sure nothing catches fire while they ransack the place.

This coup ends if and only if it create noticeable and immediate chaos in the lives of people who curently support it.

2/

When you’re working on a system (business or human!) for years, it becomes your baby. You want to protect it. You want it to survive even if you’re kicked out. Like sailors on a ship, protecting the ship above all.

But if the ship falls into enemy hands, keeping it afloat might just be the opposite of what you want to do.

Look up “USS Lexington (CV-2).”

3/

That’s a dramatic historical comparison, and look: I’m not necessarily suggesting you should actively destroy federal computer systems. But at the very least, don’t teach the invaders to •pilot• the ship before they chuck you overboard.

Let them fail.

4/

Maybe, maybe you'll even have the chance to pull a Citroën:

https://www.drive.com.au/caradvice/citroens-genius-act-of-sabotage-against-the-nazis-in-world-war-ii/

Maybe you can slow down whatever BS they’re pulling. Maybe you can install a deadman switch in the software so that it stops working if authorized people aren’t present. I don’t know.

But for heaven’s sake, don’t train in the fascists.

/end