Introduction About Site Map

XML
RSS 2 Feed RSS 2 Feed
Navigation

Main Page | Blog Index

Sunday, January 22nd, 2023, 2:39 am

Sirius ‘Open Source’ Bullying Its Own Staff

NOC for Architel
By Mike Reyher – Architel Operations Center, CC BY 2.0

Summary: Network operations centre (NOC) staff at Sirius ‘Open Source’ was subjected to intense abuse after Bill Gates had passed a bribe (even a double bribe, as we’ll explain later) and today we give another example of this

AS readers of this series are probably aware, NOC staff has always worked from home. Myself and my wife never took a day off for sickness (for 21 years), but some colleagues did. Some colleagues even worked when there were still ill. Did the management appreciate it? Not really…

Shown below is how one NOC colleague was treated a couple of months or so after the Gates Foundation gave the CEO money, though only after an NDA had mysteriously been signed (more on that in the upcoming video). This was the time the NOC staff was routinely being bullied, falsely accused etc. As if the company was hoping to scuttle the whole thing, or perhaps the unqualified managers were on an ego/power trip.

This is going back to September 30 2019, i.e. when Richard Stallman was under fire right after there was a Bill Gates/Jeffrey Epstein scandal at MIT (the media shifted focus away from that). It was also around the time Melinda Gates was pursuing a divorce, knowing about these scandals. Here is a message from the colleague:

Date: Mon, 30 Sep 2019 08:27:58 +0100
From: xxxx

I was ill last Monday on my shift and couldn’t find them after a cursory look

On 29-09-2019 13:17, xxxx wrote:
> If both keys were there, why the delay?
>
> xxxx.
>
>> On 29 Sep 2019, at 12:45, xxxx wrote:
>>
>> xxxx’s key is in puppet for xxxx and Sirius, or can be grabbed from any xxxx or sirius machine where it has been pushed.
>>
>> As was/is xxxx’s.
>>
>> In short, you’ve had both all along.
>>
>>
>>> On 28/09/2019 03:34, xxxx wrote:
>>> We’ve now got xxxx’s key so should be done by Monday.
>>>
>>>> On 27-09-2019 09:37, xxxx wrote:
>>>> Ok.
>>>>
>>>> Back to support. Please resolve this as soon as.
>>>>
>>>> Please use your investigative skills and complete this task. Read what
>>>> xxxx has written in previous email.
>>>>
>>>> It is ridiculous that xxxx and xxxx have to wait for 3 months to
>>>> get these access sorted out. I seem to be playing tennis with support
>>>> and xxxx to get this simple task completed.
>>>>
>>>> THIS IS IMPORTANT AND THIS NEEDS TO BE COMPLETED BEFORE MONDAY NOW.
>>>>
>>>>> On 27 Sep 2019, at 09:21, xxxx wrote:
>>>>>
>>>>> Well, yes, but surely easier to just grab them from any machine
>>>>> anywhere xxxx or xxxx already have access? Or xxxx puppet?
>>>>>
>>>>> No need for me to spend time looking that up when Dan (or anyone on
>>>>> support) can already do that.

[...]

What’s noteworthy about the above is that unqualified or barely-qualified family members of the above managers are involved too. This is where nepotism rears its ugly head too. That alone can make people sick (metaphorically).

A followup:

….. thanks xxxx…………………..

Now xxxx are you able to follow this or will this still be an issue?….

Kind Regards,

[...]

> Like, it’s really not hard, I’d just rather spend time doing the critical things that *are* hard.
>
>
> On 30/09/2019 10:22, xxxx wrote:
>> Hi xxxx,
>>
>> As it shows below xxxx has not been able to locate the info.
>> Can you please send this agin or direct it to xxxx where he can find these so he can do this on his shift tonight.
>>
>> *_Support, I need this done. _*
>>
>> Kind Regards,

[...]

What’s behind all this? Here comes the explanation:

Sorry, you misunderstand me. I had sickness & diarrhoea during my shift on Monday and when I tried to find xxxx’s key I couldn’t as it wasn’t on any of the machines I looked on. However I have since found it.

On 30-09-2019 10:22, xxxx wrote:
> Hi xxxx,
>
> As it shows below xxxx has not been able to locate the info.
> Can you please send this agin or direct it to xxxx where he can find
> these so he can do this on his shift tonight.
>
> SUPPORT, I NEED THIS DONE.
>
> Kind Regards,

[...]

And later this:

Is there really any need for this constant criticism? It really makes me unhappy in the workplace. I’m sorry I was ill okay?

It has already become a chronic issue at this point. It was harming a person’s health.

Here’s the reply received from the imposter ‘manager’:

xxxx,

There is no criticism applied. I am simply trying to get access for xxxx and xxxx for the last 2/3 months now. Every time support can’t find some information or other. Which surprises me every time with the amount for years everyone has worked with Sirius and these are not new tasks.
It’s very worrying that simple tasks like this are not being finished in time. No one simply takes responsibility and the tasks are passed over constantly. And no one looks for instructions and always waits expects xxxx to take over.
Can we follow instructions and keep things professional please.
xxxx

Later on there was a more detailed explanation of the background:

Please will you supply the specific times over the last 3 months where you have asked us to do this? As far as I can tell its only over the last week. I have explained that I was ill last week when I looked for the key – and I have apologised for being ill too.

And please can you tell me what you learnt on the depression course that you and xxxx went on and how you are putting it into practice? As I have said many times to you now, there a few of us at Sirius who suffer from depression and want to work in a positive environment that is free from constant bullying.

You will get the best from your team if you treat them well and with respect. Constantly putting us down will not produce the best work from us.

This “constant bullying” (I agree) did not stop after this. We were already losing key technical people at that point and the company was thus gradually losing the ability to even maintain its own infrastructure. A lot of the time we were presented with false timelines, cushioning false accusations. The blame/fault was almost always with managers, who not only drove away (or pissed off) colleagues but also failed to take action like paying simple bills.

To give one example, an important client kept having outages because the above managers didn’t even perform simple tasks like paying bills. Some NOC staff kept warning about it. In a handover to shift 2 (09/06/2021), for instance, the NOC person on duty wrote about “Third Invoice Overdue Notice” (yes, third), noting: “Concerned that they’re going to discontinue the service” (this would not be the first or last time).

The manager who did the most bullying at the time was hired not for skills or for relevant experience; it’s a former colleague of the CEO, who used to do secretarial tasks (saying anything more might give away the identity, but this is fact-checked). It’s astounding that around that time personal assistants could suddenly be elevated to management and even act like they’re bosses, clearly incapable of handling the responsibilities. Picking on ill and depressed people was their “pastime”. They fancied the idea of being in control of people vastly more qualified than them (who actually did all the real work, sometimes overnight with ‘jet lag’).

Technical Notes About Comments

Comments may include corrections, additions, citations, expressions of consent or even disagreements. They should preferably remain on topic.

Moderation: All genuine comments will be added. If your comment does not appear immediately (a rarity), it awaits moderation as it contained a sensitive word or a URI.

Trackbacks: The URI to TrackBack this entry is:

https://schestowitz.com/Weblog/archives/2023/01/22/bullying-ones-own-staff/trackback/

Syndication: RSS feed for comments on this post RSS 2

    See also: What are feeds?, Local Feeds

Comments format: Line and paragraph breaks are automatic, E-mail address never displayed, HTML allowed: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

Back to top

Retrieval statistics: 21 queries taking a total of 0.932 seconds • Please report low bandwidth using the feedback form
Original styles created by Ian Main (all acknowledgements) • PHP scripts and styles later modified by Roy Schestowitz • Help yourself to a GPL'd copy
|— Proudly powered by W o r d P r e s s — based on a heavily-hacked version 1.2.1 (Mingus) installation —|