Introduction About Site Map

XML
RSS 2 Feed RSS 2 Feed
Navigation

Main Page | Blog Index

Tuesday, January 10th, 2023, 2:38 am

Lying to Clients is Crossing a Line

One client even said it bluntly to our manager, accusing the company of “incompetence” (the examples below are only the managers’ fault)

sirius-competence

Summary: Dishonesty and non-technical problems became a norm under the new Sirius ‘Open Source’ CEO (or under his watch); today we give one client’s story as an example or a case study, where Sirius management is failing to pay upstream providers, resulting in catastrophes

THE “finaliser” of the company may not be the only misguided manager (or saboteur). He turned out to be the barrier and the burier [sic] of the company.

Today we give as an example two separate incidents impacting twice the same client, one year apart. Cause of outage? Not faulty hardware. Not faulty software, either. It was unpaid bills. Who failed to pay? Sirius. The client trusted Sirius to take care of it. Big mistake.

Without naming the client or the nature of the client’s work, let’s just say that it is a critical client, a longtime client (longest), which relies on real-time access to data and cannot afford downtimes (not long downtimes anyway; as alluded/hinted in this meme last month, the effects would potentially be devastating).

Sirius failed to pay providers in two countries. The first such incident apparently didn’t serve as sufficient warning. No lessons learned. Or maybe no money left in the bank. Remember that it also looks like Sirius could barely pay its own staff; it’s like they failed to pay our pension on several occasions/years; thankfully the pension provider started sending us more and more letters to warn us; it was waiting to report the company, maybe even impose penalties/fines as a result.

Making fun of companies or persons who cannot pay bills is no source for amusement/mockery, but if one company fails to pay another the latter may fail to pay its bills or even its staff. So that’s not fair. We’re not talking about food bills here; it’s stuff like hosting. They kept warning, repeatedly, before taking action (e.g. an E-mail saying payment was “overdue” and lots of warnings before that, for several months in fact).

Was the client properly informed about what had happened or were those incidents brushed under the carpet, swept under some rug somewhere? This is the sort of stuff that made me unhappy about the company. The latter incident happened just months ago. I decided not to contact the client and instead hope the company would confess. That never happened though. A host wasn’t being paid for a very long time and then it issued warnings which escalated in severity. The client might also want to ask this host and see if there are overdue invoices right now (in 2023). Months ago the client had a very major outage after Sirius had racked up thousands of pounds in unpaid hosting bills (while trying to sell the client AWS ‘clown computing’, which would be vastly more expensive and I internally opposed efforts to move to it).

It’s absurd that pointing out such embarrassing realities would be deemed ‘defaming’ a company (with facts). The liars love to claim that everyone who says the truth is engaged in “defamatory” behaviour, as if defamation and truth became synonyms. The egoistic boss fails to understand that a company is not a person and facts are not defamation.

When an incident happened in 2021 the handover said: “Logged onto their portal and server is suspended due to unpaid invoice. Raised it with everyone on Slack, and xxxxx told me to tell xxxxx that we’re raising an important ticket with them. xxxxx paid the invoice and they lifted the suspension.”

The Slack messages at the time:

xxxxx: Does anyone know if xxxxx has been paid yet as xxxxx says he can’t get onto xxxxx
xxxxx: xxxxx is asking for an update. Can we pay xxxxx tonight or will we have to wait until tomorrow?
xxxxx: They have a fairly old-school process for accepting payment if I recall. It took a number of days to clear payment last time.
xxxxx: xxxxx and/or xxxxx put the payment through last time to a specific bank account.

“It took a number of days to clear payment last time,” it says. Not the first time. Lessons not learned.

This is similar to the excuses we got when our pension wasn’t paid (on two separate years), even several months after the days in question. They blame the payment processor instead of those who failed (e.g. forgot) to make the payment!

Three months ago another rather similar incident happened, but this time in another country and another hosting provider. There was no mention of what had happened after the Big Boss was shuffling lots of credit cards, struggling to make a payment to the provider. To quote: “xxxxx and xxxxx emailed to say that xxxxx was down but we didn’t get any alerts so looked into it. Then one of their customers emailed to say they couldn’t login. xxxxx asked me to restart UIs which I did and the problem was resolved. xxxxx sent some questions to ask xxxxx who said he will look into it and get back to them tomorrow. I checked the db connections and there seems to be 380 open out of a possible 1000, but I’m sure xxxxx will be able to verify this too.”

Nothing was said about the failure to pay the bills. Are we meant to think nothing actually happened? Are we meant to lie to clients about this, wasting their time as they try hard to figure our the root cause?

Don’t work for chronic liars. If your employer starts lying a lot, consider your options.

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/10/crossing-a-line/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.134 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 —|