Is there a term for something similar?

My boss is injecting hopium. He barely sleeps compiling massive massive documents which don't answer anything. We literally have a "(LILR Design Language)" spec which when you keep slicing through it, doesn't actually say anything.

It takes 70 seconds to full scroll through it with the fast scroll mechanism, but the whole thing boils down to "basically if it looks good then its good".

And even worse, he is asking for access to the codebase of the product since "I can do 90% of what we need and all the devs need to do is review the PR".

What is this called?

I say give him access and make some popcorn. At my last job I watched a manager who had not written code in years start pumping out garbage PRs and reports with hallucinated stats. He would bring them to our engineering team meetings to present and we'd spend the whole time ripping into them until he got embarrassed enough to stop doing that. I can only imagine what kind of doubling down a more stubborn person could get up to.

In highly bureaucratic companies there starts to exist a value for bureaucracy ‘per se’. This can be found in endlessly growing risk and operational policies. Actually, one is lucky if the policies don’t say much. That means that the bureaucracy is trying to stay out of the way of operations. So while bureaucracy is a way of management and staff departments to fulfill their needs, the fish are still being caught.

One step up on the ladder is that the fish aren’t being caught anymore due to regulations pertaining the hooks (disallowed) and the length of the line. The fishermen complaining are being told that the regulators are also complaining and that management has decided that complaints everywhere are the best balance.

It's called: the CEO isn't staying in their lane and is injecting incompetence into the company - look for a new job.

We just got sent a document that amounted to "please set up a CNAME for us", but was multiple pages long and had detailed instructions on how to do various troubleshooting tasks before, during, and after creating the CNAME, mixed in so that it was impossible to tell what the actual request was.

Had all the classic LLM signs. Underuse of commas. No longer sentences. No other punctuation except full stops and em dashes. Just sudden negation at the end of three barely related concepts.

I'm so unbelievably sick of reading this slop. For the love of God, it's more work to turn bullet points into an unreadable multipage document, so just send me the bullet points. I don't want to communicate with a gigantic vector representing the average person's literacy anymore.

I call it executive deterministic parroting:

https://ianreppel.org/executive-deterministic-parrots/

> What is this called?

A manic episode.

Stimulants

We gave our bosses access and they mostly gave up after discovering how hard it was to get things past CI. YMMV if you have fewer or healthier tests.