4 ms·
Next, I asked an honest question: even then, why was it automatically up to me to get these things to work? There was no division of duties on the team. Everyon
by DoreenMichele 9y ago
Next, I asked an honest question: even then, why was it automatically up to me to get these things to work? There was no division of duties on the team. Everyone was responsible for the system as a whole.
So, it was up to her because everyone was responsible for the system as a whole. That includes her. She is clearly in the wrong here.
What "experiment" did she think she was running? I see no experiment here. All she did was not address the issue until someone higher up complained. That's it.
She made zero effort to find out why this happened, who did it, etc. She assumes her coworkers are wrong and bad and lazy. Maybe they were busy doing other things and didn't notice this issue. If you are more competent than your coworkers and not getting paid extra or whatever, that can be aggravating. But management doesn't care about your petty BS. They care that the system runs properly, not which individual routinely has to catch and correct the anomaly while pouting about doing their job.
She even indicates it was incredibly trivial to resolve. So this post sounds like someone looking for BS reasons to be wrapped around the axle about something.
"Once, at work, I spent vastly more time conspiratorially complaining to my boss and then faux monitoring the system than it would have taken to just fix the problem that it was my job to fix because I had delusions of grandeur and wanted to indulge in some completely pointless witch hunt."
Wow, honey, get new hobbies. Fucking with coworkers for giggles and then blogging about it does nobody any good at all.
- ModernMech 9y agoShe obviously felt under appreciated by her team, and resented the workload that hand fallen into her lap, viewing her other coworkers as lazy. For their part, they saw she did it without complaint, and obviously didn't mind that. Sure they may have been lazy in this scenario, but the author certainly didn't communicate she viewed them that way. So she conducted this passive aggressive "experiment" and then got mad when she was called out on it. This is just an example of a communication breakdown resulting in bad team dynamics. Worst of all, IMO, the author concludes not to disengage in her anti-social behavior, opting to continue doing it but this time in secret.
- DoreenMichele 9y agoShe went on a completely pointless witch-hunt. The odds are good that had someone risen to the occasion to track down the anomaly and fix it, we would still have some poison pen piece about the incident. She just would have found some different catty angle. "Let me tell you about that time I kindly stood idly by failing to do my job as an experiment to graciously let my bad and lazy coworkers grow and they completely botched it. Thousands of dollars in damage done and servers had to be replaced." "Let me tell you about that time my male coworker decided to steal my thunder and get promoted over me by doing my job when I couldn't be arsed to because sexism is clearly alive and well!" People who spend two months looking for some BS excuse to fingerpoint instead of spending 30 seconds fixing the problem are going to find something to complain about. She not only spent two months pursuing this at work, she then blogged about it. She invested all kinds of time and energy into this bizarre little scenario in her head. She clearly has Big Feels about something. Why? I don't know. But that is the real issue here.
- angersock 9y agoPolitely, you don't know what you're talking about here. If you read up on the author you get a much better picture of the orgs she's been a part of, the work she's done, and the problems she has done troubleshooting on, I think you might adjust your opinion a bit. She suspected her team was underperforming and unfortunately the quietest way of verifying that is just not to be the one to step up. There was no "witch hunt" here.
- DoreenMichele 9y agoHer stated goal of proving the badness of coworkers is clearly outlined in the title of the piece. The piece itself in no way supports the assumption she asserts concerning their badness. Perhaps it is just bad writing that neither stands on its own nor indicates that there is additional material needed to fully appreciate it. I don't feel any personal obligation to do a lot of legwork here to bend over backwards to give her the benefit of the doubt, especially since I see no reason to doubt my conclusion.
- psyc 9y agoI thought I must have misunderstood the story, because after skimming it I had the same impression. The author came across as having superiority + victim complex, and I got the impression that yes, the team has problems, but the author was toxic.
- AstralStorm 9y agoCongratulations, you've labelled the author exactly as she did other people. (Labelled, pigeonholed, same thing.) This is how these things get started, people label each other in a bad way then force them to stick to labels. (In a soft way or more explicitly.) There is no good way out of such situation. If you point it out you're labelled as disruptive, because status quo is God. Even more so if you escalate. If you take initiative, get labelled toxic and evil. If you quit, you're a quitter or job hopper.
- DoreenMichele 9y agoThere are good ways out. The fact that she and you have no idea what they are notwithstanding.
- AstralStorm 9y agoPlease name a few of them. specifically ones that will result in a good situation for all involved. I'm actually interested and not being obtuse here.
- DoreenMichele 9y agoYou decline to fit the label. You decline to accuse the labeler. You treat it as a communication problem. You starve the drama of attention. You prove them wrong by failing to be guilty of the accusation. You assume the first several incidents are unfortunate happenstance.
- diyseguy 9y ago
- lhorie 9y agoThe part that struck me as particularly strange was: > he just said "the documentation sucks". My response to that was "uh, well, I figured it out, so how bad could it be?". Isn't common sense to update the documentation for how to do semi-obscure dev-opsy things and disseminate this information to the rest of the team? There will always be some plumbing thing that you are the most familiar with; if you want the team to take shared responsibility, it's kinda up to you to bring it up and suggest rotation or whatever needs to be suggested to systematize the workload distribution.
- taneq 9y agoI interpreted her response as "the documentation is adequate, so the problem lies elsewhere."
- geggam 9y agoSame, her coworker also said they were aware of the issue but did nothing about it nor were they inclined to ask how to fix it.
- sidlls 9y agoWhy is her standard for "adequate" superior? We're to assume it is, apparently, but it isn't clear that it actually is adequate.
- taneq 9y agoWell she did figure it out from the documentation, so clearly it was adequate for her. Maybe she's just that much smarter and more competent than her colleagues, and what's adequate for her is not adequate for them, but if so then that somewhat justifies the frustration that caused her to run her little experiment in the first place.
- sidlls 9y agoIt doesn't justify her frustration at all. There is no indication she tried to help (e.g. by teaching, explaining the superiority of her method, etc.), ever. Her frustration would be justified if she'd been acting like a senior, experienced person and constantly met with ambivalence or incompetence, but there's no indication of that in this blog post. Her frustration absolutely does not justify her actions anyway so I'm not sure it's relevant.
- ericmcer 9y agoI mean her job is not specifically to make the team function well. The person whose job it specifically is, her boss, totally flubbed this one. An engineer came up who was clearly having issues with the team and his response was to just sit back and watch it happen.
- DoreenMichele 9y agoThere were, no doubt, genuine problems at her job. This was not a good way for her to handle it. Setting out to prove you have bad coworkers is unprofessional and just not a good thing to do. I had a really lousy coworker at my corporate job. I hated being assigned his botched files when he took the day off. Management figured it out for themselves and eventually fired him. If you have so little faith in management that you think they won't find the bad eggs themselves, you should be job hunting, not setting up little experiments to prove they are bad. If she was dissatisfied with always being the one doing this 30 second job, there are far better ways to try to address it. This is not it. The post is several years old. Hopefully she now feels "Gosh, I was young and stupid and can't believe I did that."
- maxwin 9y agoI would not want to work with her and would not want her in my team.