Sorry you suffered that experience though, hope you made it out of there.
The book is in my opinion a distillation of those skills, which -- maybe just so happen to -- come from military background. None of what is presented in the book come anywhere close to the situation you described. I would dare to say, quite the contrary. It is about listening, understanding, trusting and many other things, usually considered positive.
It had a great influence on me, though I have never even thought of joining the military.
I started practicing extreme ownership as a regular developer and made my way up to a team leader in about 6 months time. Now I double down as a fresh (and young) leader.
2. Common sense dictates that whenever one transfers skills to a new context, one assess the underlying assumptions and context of those skills to adapt them for use. I'm sure mistakes in that regard will inevitably be made, but I give most people more credit than to assume, a priori, that people will transplant those skills without any thought given to changing contexts. That seems like a very condescending assumption to start with, but maybe I'm misreading you.
> Skills learned in the military are for war, learned for conflict situations and applying them to civilian environments and bringing a war mentality or attitude to a workplace is toxic.
> only adds to the toxicity of a workplace
What exactly was the toxicity besides your choice to overreact (stay overnight) ? Why do you believe that leadership skills for war are not applicable to other domains?
So it sounds like OP was coerced to do so and it was not a free choice or an "overreaction" as you characterize it.
"If I wanted the outcome I was aiming for I had to.... (workout?)" This is how I took the sentence. A totally volitionally accepted responsibility
It was not a choice. It was an order.
One day after a major release stuff broke in production. The company was losing customers daily. The "superboss"-es from HQ descended on our little dev team in a small midwestern city and ordered "Code Red".
What it meant to me as a new dev was that I can't go home and the whole team had to stay in the office until the problem was solved... A part of the team had to sleep in the office for a few weeks. (I still don't know if this is against OSHA.)
Many years later while I was watching the movie "A Few Good Men.", I learnt that "Code Red" was a military term. Suddenly, it dawned on me that my "superboss" was also an ex-military person.
Sleeping at work did not fix the issue, after many months of hiring help and bringing in more hands the outage was brought under control.
Did the ex-military "superboss" help the situation? I don't know...
Now I know that Military veterans in their enthusiasm to find work in civilian environments tout their ex-military skills as team building or leadership skills.
Skills learned in the military are for war, learned for conflict situations and applying them to civilian environments and bringing a war mentality or attitude to a workplace is toxic.
I don't have an answer to what makes a good technical leader but I know from experience that ex-military style leadership only adds to the toxicity of a workplace.