Introduction About Site Map

XML
RSS 2 Feed RSS 2 Feed
Navigation

Main Page | Blog Index

Saturday, December 17th, 2022, 5:48 pm

Sirius Open Source Sinking in Debt

2018 and 2019:

Sirius 2018 and 2019

2019 and 2020:

Sirius 2019 and 2020

2020 and 2021:

Sirius 2020 and 2021

Growing debt, no money left in the bank.

Meme of koala says Sirius-ly; Looks like money has run out (logo added)

Summary: When the founder of Sirius ‘Open Source’ divorced his wife a new company was formed, almost cashless; there was a lot of debt, but workers could not ask about it

TRUTH be told, the state of Sirius has not been good for years, but treatment of staff worsened a lot after management had changed. Then, there was a tendency to blame staff for failures, even if and when the failures were attributed to actions at the very top. Below we present part 2 of the relevant section of the report. As shown above, as the years went by the company was running out of money and out of time (way too much debt). These figures are all in the public domain. The lesson of the story is, desperate companies may resort to bullying, and the bullying would then be directed at anyone but the management.


The company had not shared with us financial information or contract details (amounts of money) in about half a decade. Financial statements are publicly available, however, in the public domain.

Apparently there was something in the wiki when the CEO’s ex-wife was around, but it’s all gone now. Is the company heavily indebted to a bank? According to the latest statement, the company is very, very deep in debt. Notice witness in the financial documents of the bank: the office manager. Even at that point the company understated the severity of the situation as debt grew every year despite a significant cut in the number of salaried staff. Some names/signatures are rubbed off, but maybe those aren’t relevant. The CEO’s ex-wife is not listed in some of the recent documents. One is left guessing aimlessly. Transparency would be much appreciated.

The office manager refused to tell Roy why the CEO had relocated or was based in the US and was repeatedly evasive when Roy asked. Workers were not told why the company changed registration (like a new company minted; new contracts needed to be signed), so some speculated that post-divorce ownership may have been a motivation. Those were dark times for the company with many questions hanging and an absent CEO, at one point showing up in a rib shirt for a company meeting online. This felt rather inappropriate.

Those observations may not be pleasant to see or hear. But those are very important and they hopefully help explain a certain change in attitude. For instance, the company’s use of Slack probably violates privacy law associated with some of our clients, never mind our own. We are aware of several colleagues who may have left due to management being rude and unpleasant.

The harshest bit was, after key colleagues had left the bullying from management intensified, taking out frustration on the wrong people. For instance, Roy and Rianne were sent to be interrogated. The HR agency that interrogated Roy and Rianne (this lasted for nearly 3 hours!) totally sided with Roy and Rianne and asked important questions about the management; the HR people urged Roy and Rianne to keep record of everything and assumed this thing was likely politically-motivated (or similar). In other words, this backfired spectacularly on the accuser and moreover cost the company a lot of money, never mind the moral damage. No clarify or apology was consequently issued to Roy and Rianne. The accusers were not punished this this misuse of company budget and one remains on the payroll to this day. What are decent people supposed to expect from a company that treats veteran (long-time staff) like that? By that time, Roy had been in the company about 5 times longer than the principal accuser. Roy was encouraged by HR to keep documentation for self-defensive purposes, as per this document.

Saturday, December 17th, 2022, 9:33 am

Sirius Drove Out the Staff

Video download link | md5sum ed8d64d30480b43b0b9fbbe627e0a9bf
Bullies as Managers
Creative Commons Attribution-No Derivative Works 4.0

Summary: Sirius turned from bad to worse; as debt increased and further loans were being taken actually essential workers were leaving and earlier this winter the company registered as its accountants’ address (envelopes are sent from an unregistered address, probably someone’s apartment near London or Bristol)

THE sad story of Sirius ‘Open Source’ has been told here for a fortnight already. It started two Saturdays ago. In the video above I sum up the latest two parts in the series. We’ve covered about a third of the material so far.

The short story is, the unqualified “managers” at the company (following tragedy and ordeals in the personal life of the founder) decided to assign classic “bullshit jobs” (tasks which serve no actual purposes), falsely accuse people, steer the company away from “Open Source” (which they neither understand nor use) and it didn’t take long for the most important technical staff to leave. As a result, the company’s infrastructure could barely be maintained anymore, hence outsourcing was seen as imperative. The sad thing is, innocent people were being accused of things they had not done, and tasks previously done by people who left (could not stand the new “managers”) could not be completed. It seems like a miracle that the company even survived until the end of 2022, albeit with very heavy debt and a dodgy corporate structure. Its current registered address is actually the accountants’ address (outsourced, obviously!).

Sirius Open Source current registered address

This is not the company’s address. The accountancy firm is based in this address.

Friday, December 16th, 2022, 4:53 pm

Sirius Open Source: The Brain Drain Started Years Ago

A koala model bullied: Bullying staff of Sirius instead of doing actual work?

Summary: Around 4 years ago some of the most essential staff of Sirius Open Source suddenly left the company, even at short notice (the management was trying to hide this, but abstaining from any remarks on this matter became unsustainable); it’s probable that abusive management played a considerable role in this ongoing demolition of Sirius Open Source

THIS part (one of 4 in the corresponding long section) deals with the beginning of the end of Sirius ‘Open Source’, which began to do irrational and occasionally dubious (maybe illegal) things, leading to the collapse of the company and coinciding with the collapse of the founder’s marriage. A certain “management cabal” was covertly forming, based on perceived loyalty if not kinship, publicly insulting the former manager and former wife (who even contacted clients after the divorce) while treating longtime staff like rubbish. It was about 4 years ago. This part does not deal with anyone’s personal life, but it’s impossible to understand Sirius and its unfortunate demise without grasping that issues in the personal life of the founder triggered a whole bunch of commercial issues, and management vacuum was hurriedly filled up by incompetent bullies who lie to everybody and never admit mistakes. These people don’t know how to manage, were never trained in management, and they compensated for inner insecurities by acting aggressively against sceptics.

There’s this quasi-twofold issue: as the company employs based on nepotism, in spite of a lack of any relevant qualifications and/or experience (even managers; they don’t know “Open Source”), the company ends up with nontechnical Windows users in technical roles. This means clients cannot be wooed — or existing contracts secured/renewed — for technical tasks, so the nature of contracts becomes increasingly clerical — not technical — and as Windows has back doors among many other security problems the whole security model becomes farcical. On issues pertaining to a lack of skills and nepotism, please stay tuned until next month.

In a nutshell, as this section shall hopefully demonstrate, the management of Sirius basically destroyed and dismantled the company with years-old failures and an endless string of bad decisions, lacking any consultation with those impacted, who are also proficient. And why? Well, because to the “cabal” it is a vanity project; they know everything! And at the same time they know nothing. Sadly for them, eventually they end up without a company, without an employer, without a job of their own. So well done! Own goal.

As somebody explained to me earlier today, sometimes people are blinded, and more so if they’re upset and angry. They’re too confident and the ego is becoming way too big, and hence they wear blinders and see nothing else that may make actual sense. Due to emotions and impulses they destroyed the company. It’s too late now. They recently discovered that they had destroyed the company and now they focus on how to try to not only suppress this series but also remove anything that was published so far. This isn’t a company run by grown-ups but by cartoon-obsessed and over-confident “superheroes” (in their own minds).

Here is the first part of the section in the report. It is entitled The Bullying Era because bullying is what best sums up what was happening back then. Not bullying among staff like peers and colleagues but bullying from the management (i.e. top-down), along with false allegations, accusations, and sometimes fabrications.

In this first part we present some background about the status quo around 2018. Later we’ll show some bullying examples.


The Bullying Era

This section is essential. Without it, the sentiments of Roy and Rianne or their relationship with the company cannot be fully grasped.

Several years ago there was management change. It seems to have resulted in the company becoming a lot smaller and poorly managed. Staff did communicate some of the concerns, as those concerns were shared across teams and colleagues (unionisation is difficult in very small companies). To quote one message seen: “I’m gratified to know you’re with us in all this. We’re a lot stronger as a group. I regret to see we’re all being bullied, typically with bogus allegations and our health is affected. I did face the management over this, albeit privately.”

The management likes to think it lives in a tall tower on a hill, enjoying total control over minds and hearts. But when many people get treated very unfairly and truly badly they’re likely to talk to one another.

Preliminary research helped elucidate pertinent facts about the company. There was a list of things we know and things we would only speculate about at that point. Facts:

– When Roy joined the company his per-hour rate was higher than now (almost 12 years later). Some colleagues receive different pay for the exact same role. For instance, some years ago it could be confirmed that some overnight NOC staff received a salary of 21,000 pounds per annum, whereas colleagues got paid about 25% more. They did the exact same role.

– a key colleague no longer appeared to be in the company, as confirmed (we believe) by the VPN renewal table. Roy warned or politely cautioned management not to lose technical staff and named him specifically.

– One colleague once spoke about being “shareholder” or similar with the CEO, but this was not communicated to any of the colleagues.

– The CEO was angry at a long-serving colleague when he left, one might only suppose due to the very short notice. Managing core functions at the company became almost impossible and some clients could not be served, resulting in complaints later mis-attributed (wrong people blamed rather than those who lost the principal colleague).

– The Sirius office was, at that point, virtually empty and must have cost at least a grand a month just to rent (workers were almost sure it’s rented, as the shutdown in 2020 helped confirm). This seemed like a mis-allocation of funds or priorities.

– Company meetings were canceled without any reason given — not a positive sign at all.

– No transparency about departure of workers. One had to guess or rely on gossip.

– Some colleagues, who had more inside information (because of physical office access), decided to leave the company

– Moving to AWS was about lowering costs, but those costs have (expectedly) risen to something comparable to a salary, set aside issues associated with autonomy, privacy etc. This was short-sighted.

– Moving or changing the NOC’s night cover from 4 people to 3 people was also about lowering costs, but that meant really awful and unhealthy sleeping patterns for all those involved. Despite assurances this would improve, nothing ever happened and no redemption came. People who work in daytime cannot fully understand what it involves to work overnight and change the night hours half a dozen times a month (like jet lag, maybe even worse due to short intervals).

– The new manager knew the Sirius CEO for a long time (circumstances or context not fully known but it may be professional, like the Open Source Consortium, which the CEO claimed to be the leader/founder of but apparently wasn’t; there was a mis-representation in the press; Roy met the person behind the Open Source Consortium, who wished to point out he had wanted to sue the Sirius CEO for defamation over it but said it would be too expensive and thus unworthy of pursuing).

– At some time around that point the Director of the company (in the UK) was US-based and even insinuated to staff that many NOC operations would be shifted to the US (that never actually happened).

Thursday, December 15th, 2022, 4:53 pm

Sirius ‘Open Source’ Managers Sitting on Their Hands While Moaning About Workers

To manager at Sirius ‘Open Source’: What do you do all day long anyway after I work all night?

Summary: Following this morning’s example of lying to clients at Sirius ‘Open Source’ let’s examine how the daytime team, i.e. self-appointed “management”, fails to deliver work which was promised (Sirius promised a project months ago, but nothing got done) and ‘low-level’ staff took the brunt; are managers doing anything at all? What are they doing all day long? Pretending to be busy? Collecting their salaries? Pushing around people who work all night long and actually possess technical skills?

As shown yesterday (or around midnight), managers at Sirius are directing staff to lie to clients and sometimes also lie to the staff. This is a highly toxic workplace climate. It compels good people to abandon good principles. Meanwhile, the ‘bosses’ are not — or barely — responding to E-mails (clients’, staff E-mails…), not doing basic accounting properly (not paying pensions sometimes!), so what on Earth do they even do all day long? Are they testing the position of their chairs?

Based on company meetings (2022) and public disclosures from the same year one can imagine the situation is rather dire; these show that there’s barely any money in the bank (we’ll show evidence at a later point in the series).

It’s hard to know what exactly happens behind the scenes (no transparency), but there’s maybe a ‘race condition’ against clients’ payments (revenue and salaries for staff). While almost understandable, this means that the company starts doing potentially illegal things when it comes to finance (we’ve mentioned stuff like a lack of payslips).

There are many other dodgy aspects we’ll explain at a later point, e.g. nepotism and contract-signing at ‘gunpoint’ (the concept will be properly explained some other day).

Nighttime staff at Sirius is working hard for a very small salary. It’s only reasonable to expect management to do the same. Moreover, meeting clients’ deadlines or expectations is rather fundamental (the previous parts mentioned SLAs).

In reality, however, everything is reversed; those who are failing at their jobs try to finger-point elsewhere and outwards. They aren’t subjected to any inside or outside scrutiny (e.g. for failing to attract good clients). To hide their incompetence they resort to spying, dirt-digging, and misdirection of blame, in essence improvising with the “law” and basically flinging lots of crap, hoping something might stick to an anti-adhesive frying pan. Last month we decided that “enough is enough” and below is one example among many more that exist. It shows how a project (not the nighttime staff’s) wasn’t being delivered for a very long time.


More Examples of Poor Service Delivery

More recently, there were more incidents of vastly delayed responses. Management received escalations but took no action. Rianne was covering the daytime shift when this (heavily-redacted) ticket was reported (note dates):

June 30, 2022

- Ticket#1013535 — RE: ?????????????????

Ticket acknowledged, escalated to ????????????????? because we may need ?????????????????. for this. The certificate, on the other hand, is valid and has not yet expired. Perhaps we can start looking for errors in that idp process log files?


July 17, 2022

Ticket#1013535 — RE: ?????????????????

Emailed ????????????????? regarding the priority of this ticket.

Dear ?????????????????,

This ticket has been open for over two weeks. Support/????????????????? conducted an initial investigation into the reported issue, but we have yet to contact the customer to provide our analysis or recommendations on the matter. When was ????????????????? available to investigate the problem?


July 30, 2022

Ticket#1013535 — RE: ?????????????????

The URL is now working: ?????????????????.
Support has not had the opportunity to update the client (no word other than acknowledging the ticket and conducting some research). I have asked ????????????????? if we can close this ticket quietly.

Hello, ?????????????????.

The URL that they reported as broken is now fully operational: ?????????????????.
I’m not sure when this problem was fixed. Support has not had the opportunity to update the client (no word other than acknowledging the ticket and conducting some research). I guess we’ll just close this ticket quietly.


October 16, 2022

Ticket#1013535 — RE: ?????????????????

????????????????? – is working for me without connecting to the VPN. Same result as what ????????????????? was getting.

As far as Rianne can remember, she brought this ticket to ?????????????????’s attention on Slack on that day (June 30th), but as usual ????????????????? is a very busy man and ????????????????? is not a big client, so it’s not of high priority. One can easily notice how long this ticket remained open/unattended/unnoticed for. This went on for so long (until October). As far as one can tell (based on what’s last known), this is still an outstanding ticket. It was open until the very last day Rianne was working in Sirius.

Finally, below is one more incident that shows one client that got truly pissed off. There are many redactions, but if scrutiny arises or one of those implicated are interested, we’ve got the full conversation. It’s meticulously documented for support.

The short story is, Sirius promised a project and didn’t deliver it, so the client began to chase Sirius. This is an example where a client has no idea who really works in Sirius e.g. in-house or associates (the Web site misleads about who actually works in Sirius):

Re: [Ticket#1013727] ?????????????????

10/08/2022

Hi ?????????????????,

I hope you are well.

Since our last meeting a month ago, we are already planning and working to update our infrastructure to Ubuntu 22.04LTS and so MySQL servers 8.

In the last few days we recorded performance issues on our master server.

I would like to ask if you can speedup your proposal for your execution and evaluation of MySQLtuner on our master/slave servers as suggested by ?????????????????. We must maintain our systems stable and reliable until the migration to MySQL8. (estimated by end of this months). Moreover, will give us the opportunity to setup the new servers with the right parameters.

Best regards

?????????????????


06/09/2022

Hi ?????????????????, ????????????????? and ?????????????????,

I think we have a very bad [this word was highligted and bold in the actual message] case of an important piece of work becoming urgent. We have had 5 database issues that have caused issues and outages in the last 4 weeks, including one yesterday.

My understanding was that in the meeting on 7th July, two months ago, you had agreed to prepare an estimate for running mysqltuner on our system. We are now in a situation where things have become critical and our ability to make system changes based on the results of this work is closing. Any changes need to be specified, developed, and tested and that usually take weeks to perform.

Please can you make arrangements for someone to assist ????????????????? on the the execution and/or analysis of mysqltuner urgently (today or tomorrow)? [highlighted and bold in the actual message...emphasizing the urgency.]

Thanks,

?????????????????


Hi ?????????????????,

????????????????? and ????????????????? have both escalated the urgency of this issue and many apologies that we haven’t addressed this faster.

We will of course support the urgent work on this mini-project and will just let any paperwork catch-up. ????????????????? is available.

?????????????????, could you please confirm your availability the rest of this afternoon and tomorrow from 2pm and we will find something that fits?

Many thanks,
?????????????????

09/09/2022

?????????????????, we would like to run that process in stage first – but we do not seem to have access


Can anyone on Sirius call me on the phone, please?

I cannot be helpful in this way.

?????????????????


Hi ?????????????????,

As below, ????????????????? is going to run this now and attach the output as soon as finished. Would you still like someone to call you?

We can do that now if you’d still like a call.

Thanks,
?????????????????


Hi ?????????????????,

it was no longer necessary when ????????????????? confirmed that you were able to access to the system and run the command requested. I have been very confused when ????????????????? said ” – but we do not seem to have access -”

Many thanks to ?????????????????.

Best regards

?????????????????


Hi all,

what exactly the problem is? You should have access to ?????????????????.

?????????????????

This is a very recent example. The client said: “My understanding was that in the meeting on 7th July, two months ago, you had agreed to prepare an estimate for running mysqltuner on our system.”

More than two months later there’s no progress.

Thursday, December 15th, 2022, 8:55 am

Don’t Work for Companies That ‘Normalise’ Dishonesty

Video download link | md5sum 5f20cd7cd1b5535c8b2fa3f78ac9179b
Sirius Does Not Accept Facts
Creative Commons Attribution-No Derivative Works 4.0

Summary: When staff is being lied to and clients are being lied to maybe it’s time to leave the workplace, for risk of becoming complicit in those lies

SOME hours ago we shared an example of Sirius ‘Open Source’ staff being told off for stating the truth or being honest with a client. We’ve sadly come to a point, especially this year, where the company was mostly about optics (like hiding its true financial state) rather than substance. Bad decisions had been made for years and nobody took responsibility for those bad decisions; worse yet, there were lousy attempts to retroactively justify such decisions.

I left at the start of this month and now I get to tell my story. My story is probably similar to many other people’s especially in the technical domain or “IT” sector; many people may experience the same things at a current employer or maybe experienced those things in past (prior) employers.

Thursday, December 15th, 2022, 2:35 am

Lying to Paying Clients, Not Just to Staff

Service-level agreement

Summary: Service Level Agreements (SLAs) or service-level agreements weren’t met by Sirius ‘Open Source’; it was often the fault of the management, but it will never admit this

THE series has thus far not given many concrete examples; nor did it name any clients. It’s never the intention to name any clients at all. This series is not about clients of Sirius. However, to demonstrate some of the failures this past year, consider the following examples from the internal report.


Examples

In recent years, in addition to the above, colleagues were compelled to become less honest with clients, all for the sake of saving face. In fact, there are countless examples of ‘cover-up’, but the following portion gives just one example (with redaction for privacy reasons).

Client chasing Sirius twice:

May I have an update on this please? I am on holiday next week and would have liked this resolved.

Thank you.

Kind regards,
?????????????????.

Later:

Just realised that this is still outstanding, any news please?

Thank you.

Kind regards,
?????????????????.

Sirius staff:

EXTERNAL EMAIL: Do not trust links or attachments without checking.

Sorry ?????????????????, the person looking into this has gone on maternity leave so this ticket must have been missed. As far as I’m aware the disk will be replaced by ????????????????? as its under warranty but we need to know the serial number of the failed disk. Is this something you could give us?

Thanks,

Sirius staff to Sirius CEO:

Hi ?????????????????,

Can I be honest with him and say I did flag it up but people were too busy? Or something else?

Thanks,

For brevity’s sake, this one example may suffice for now.

To be clear, there’s lots of wrong stuff here, more so than ‘wrong’ staff, as this makes pertinent staff look bad, even staff that does good work, causing staff to feel dishonest, in effect lying to oneself and lowing personal credibility among clients. This point will be revisited in the last section.

Nobody wishes to believe he or she works in a company that deceives the press, the clients, and even its own workers. False promises, false explanations and fictional excuses contribute to a climate of suspicion and distrust. A year ago there were unfulfilled expectations of weekly updates about what the company was doing; it only took about a week for such promises to fade away.

Tomorrow we’ll give examples of failing to meet Service Level Agreements (SLAs) or failing in other aspects.

Wednesday, December 14th, 2022, 7:30 am

‘Open Source’ Does Not Mean Pay Minimum Wage

Video download link | md5sum 1fe1eded7d9f86eb35d52fa67e17003e
Sirius Does Not Understand Overnight Work
Creative Commons Attribution-No Derivative Works 4.0

Summary: The company that goes by the name Sirius ‘Open Source’ perhaps feels like even employees are almost like volunteers or people to be (re)sold cheaply to rich clients for hard labour done overnight

THE above video is a lot longer than expected, but it hopefully does capture some of the nature of my job (since February 2011). This year it got yet worse because a person with connections to management suggested lowering the salary of people who work night shifts — people who saw no increase in salary for well over a decade! The conflict of interest here goes further than this, but that’s a subject to be covered another day.

To make matters worse, one colleague who came from a foreign and relatively poor country was paid only 21,000 pounds per year (less than peers who do exactly the same role) for a technical overnight job despite having a Masters Degree and having a lot of experience (seniority). He lives near London, so this kind of salary is barely a living wage. Seems exploitative. Is the company milking technical people?

Real-time Posts

Posts by @schestowitz

Retrieval statistics: 23 queries taking a total of 0.189 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 —|