Edit: I made some logical comment about doing something useful with half that time but deleted it because it would be hypocritical.
2. Stick to the facts: what happened, and what should have happened instead? Remove all the noise such as blame, emotional reactions, etc. Less drama, more clarity.
3. If the root cause is something dumb such as the hotel WiFi, close the ticket as "can't reproduce" and add an explanation.
You can avoid reading the text, then use a LLM prompt such as: "Can you rephrase this removing all emotional reactions and extracting only the parts that relate to reproduction steps".
Do not waste energy on toxic people. You are not a therapist, an emotional support animal, a sandbag or a doormat. You are a software engineer.
Unless you are getting rich you should avoid working there.
Criticism is fine, when it is constructive and done with tact.
Out of curiosity, what kind of background did your toxic boss have? Is it technical or business side?
I have a couple hunches for why this happens: 1. These people are dreamers and dislike people who bring them back down to reality, even if they need those people to actually build things.
2. They feel superior to people on the ground doing the building. Like they're above getting their hands dirty.
I've certainly seen my fair share of these types - too busy (ie. lazy) to really get stuck into detail during a project even when invited to do so, but very quick to point out an issue after a few minutes of expressly looking for one when it's too late.
They seem to see it as demonstrating their experience and superiority over others ie. "I only need a few minutes to find an issue". In my experiences, they also tend to insist on saying "everything needs to go through me", but never make time to follow through - out of laziness. This gives a high ROI on effort expended to stress created.
The best times I had with these people (when I was beyond caring) was laying low and doing launches semi covertly, so that there was time for clients to provide positive feedback and praise first. Then play dumb and deliver news about launch and feedback as a package.
At least to me, one of the defining bully characteristics is an inability to moderate their own behavior, even for their own benefit.
Then, the people to whom the actual task of implementing it was left can’t deliver the grandiose perfectionist idea, and the narcissistic boss can and actually wants to fiercely abuse their power over them in order to feed on the high of superiority and control over them. It’s the perfect position for this kind of person, they can feel high all the time (eventually the tolerance will kick in and the boss must leave though but this can take some time).
Organization-wise it’s a bad boss really. It’s the job of the creatives to come up with great ideas, then the boss should moderate that working together with the feedback from the implementers. Instead the boss is due to personal weakness too suggestible against the creatives and puts the damage of his own making on to the team with bullying.
I worked for a non-toxic-personality friendly boss of this type. Took me a long time to figure out how to manage upward in that case. Everything that had worked with previous "builder"-type bosses seemed to backfire and I wasn't sure why.
Because the personality was good it was especially frustrating. Deliver stuff on time without bugs or surprises, but still fail to change his mind about ambitious-yet-unrealistic goals, or put a dent in his confidence in (and preference for) the "idea people" feeding him similar goals in hypothetical-land. "But really, if you'd just build [vague idea], we'd be golden!"
Hence why telling truth to power, in a productive way that gets things done, is an important skill.
Do you remember any of the thoughts or techniques you used to shake it?
Corporations should start screening for personalities like this. They’re sick, and often seek out positions of power.
(Doesn't sound like a bad middle-manager that snuck in through the cat door. But I could be wrong!)
when someone who is like your old boss (i think a huge percentage of people are) finds themselves in a situation where their mistakes are unambiguous and obvious they panic and have an identity crisis. most people do not live with the accountability of their mistakes like people who make and do things with unambiguous results. it would be great if more people did, but in a way, thats the whole point of those "ideas" / bullshit jobs, to insulate you from your mistakes.
I used to enthusiastically throw myself into projects and other endeavors, but over the years, as it became impossible to think, focus, motivate myself... for nearly a decade, things have only been "possible" until I attempt them, find myself unable to, and end up crying in my bed for the five-thousandth time in my life.
To a point where even when I'm a bit better, I'm perpetually trapped in this "hypothetical space", never trying to do anything for real. Using my energy to dream about a better life and life goals in lieu of as much as lifting a finger to do any of them.
It didn't matter how polished our product was, he'd find a way to tear it apart. When he'd have a bad day, he'd start picking apart a random team's product. "Unbelievable!" he'd say in Slack, dropping a screen recording of the app that showed something we were supposed to be embarrassed about. It could be that the app took 3 seconds to load and show fresh data from his hotel WiFi, or it could be as simple as the UI not matching some directive he gave to the UI designers who failed to update the designs or tell us about the change. He would rant about how disappointing we were. At his worst, he fired some people on the spot for a problem that wasn't even their fault.
I quickly learned that the only way to avoid that pain was to not ship anything. The people he liked most were the ones who were operating in hypotheticals: The people who made UI designs in Figma, or the architects who drew nice diagrams about how things would work, or the people who wrote long design documents to hand to other teams. They never shipped anything for him to critique, so he thought they were the geniuses of the company. As long as they could avoid having to actually implement anything, they continued to be favorites.
It took me longer than I like to admit to shake that habit when I finally escaped. I found myself delaying shipment, pivoting from design doc to design doc, and trying to operate in that hypothetical space as long as I could. Fortunately I learned to get over it, but it was scary how much that single job could shape a large part of my personality.