"How Companies Are Shifting to Multi-Cloud" is almost certainly a half-assed take. @acloudguru confirms it by failing to retitle their marketing funnel from the "Cloud and the Public Sector" version.
Thankfully this thing is only 16 pages and starts by highlighting a point of commonality between @awscloud, @Azure, and @googlecloud: their complete lack of tolerance for taking artistic license with their logos.
We begin the multi-cloud report with a bunch of @awscloud specific technologies, though @googlecloud eagerly claims ownership of the "shitty YAML" parts.
...and Microsoft Server licensing, and Microsoft Consulting revenue, and Visual Studio...
But why mince words? I'll accept that @Azure is a going concern if you do. Let's move on.
"Multi-cloud is a thing because a 25K employee company and a 200K employee company are using both AWS and Azure somewhere internally" is... less than convincing.
This chart demonstrates that @acloudguru offers zero courses in data visualization.
"Multi-cloud is here!" is one interpretation.
Another is "corporate IT has discovered cloud" but that doesn't excite the peoples.
The deepest cut by far is putting @OracleCloud and @googlecloud on equal footing and I'm totally here for it.
A clearly emerging cloud trend is uptake of @flexera's Garbage Piano Histogram visualization.
"A third of our customers use us due at least in part to partner incentives" says much, absolutely none of it good about any provider.
The mixing of "Hybrid" into "your first cloud infrastructure" results is a practice known as CloudWashing and is commonly used to make the actual data you've gathered completely inscrutable.
I point out that @acloudguru offers 12 pages of courses on Azure, 66 pages of courses on AWS, and 6 pages of courses on GCP.
And then polled the people who pay them about what clouds they need expertise with the most.
I wonder if Former AWS Head has a name. And if he does, isn't he supposed to be taking over Amazon at least 3-6 months after this report was published?
Oh well. Azure good!
In a stunning upset, @acloudguru discovered an upward trend of their customer base towards @Azure while they were ramping up to be certified as an Azure Training Partner (last December).
Truly this must be pure coincidence.
All of this leads to the inescapable conclusion at the end of the report that-- BUY @acloudguru TODAY, THE END! says the content writer who's paid by the word and just hit quota.
96% of their business customers who hadn't fired them before 6 months saw improvement!
Now, I want to be clear on a few things.
1. This report is beneath @acloudguru's normally excellent standards. 2. We are happy ACG customers at the Duckbill Group. 3. Azure adoption is absolutely on the rise, but so is every cloud.
ACG: "How do we get a bunch of eyes on this new report we had to slap out due to partner requirements? Paid promotion is expensive."
@forrestbrazeal: "Give me edit rights and hold my tea. *clickety clickety* Watch this."
• • •
Missing some Tweet in this thread? You can try to
force a refresh
“Telemedicine” is a $100 billion market that will be worth every penny when you need a quick excuse for your roommate when they walk in on you showing your butthole to your webcam.
Site Reliability Engineering is just DevOps with better gatekeeping, which is just sysadmining with a better paycheck.
The first donation is in. Yay, the system works. That's because @charitywater clearly doesn't use a service mesh, which is the first victim of the snark.
Service meesh are fundamentally thin layers of abstraction on top of DNS, which is a database. The reason for this is purely to shut up the "it's always DNS" brigade. Now it's the service mesh which nobody understands either, but at least this time they're honest about it.
“The Duckbill Group” is next. Sweep away the fancy language and the marketing; what you’re left with is “Dramatic Readings of Excel Spreadsheets.”
One of the reasons job descriptions are hard to write is because they’re not just about the role, they’re about what you’re signaling—whether you realize it or not.
You're often too close to the role and fail to recognize what makes your company distinct.
I mean, we don't do on-call at the Duckbill Group because why would we? But I forgot to mention it in a draft of the job req, and the candidates we want are often mired in on-call hell.
"We're fun, so we should make 'a sense of humor' mandatory!"
Yeah, but "must have a good sense of humor" is often used by some incredibly toxic workplaces to justify shitty behaviors, and candidates are sensitive to that.
This is a *great* question that deserves its own thread.
The context is "I help companies polish reports like this to relevance before publication as an analyst gig; how is that not a shakedown / extortion racket?"
To be clear: the analyst engagements for things like this are very much "I will basically mock the thing you're building, only early enough in the process that you can fix it before publication."
This has definite value to the company; it makes their thing resonate better.
"How is this not extortion?"
Because you're not looking deeply enough. Read the thread I just did. It called a bad report bad, and that's true--but it didn't disparage @acloudguru's actual company or value proposition one iota.
"You're hurtling down a snowy mountain. A dangerous ravine is to your right, a dark forest is to your left. You have a decision to make. Are you on skis or a snowboard?"
"Here's a phone number and a passcode. At the beep, leave your best idea of what a dodo bird's mating call sounded like."
So I've had a few people ask me to opine on how to find your first client when you set out on your own.
My initial inclination was "people aren't going to want to hear this," which means it's probably rife for:
A thread.
Let me start by talking about my first client when I set out on my own.
"Corey, I have this problem. You know how to fix problems like this. You just left your job; you've probably got some spare cycles. What do you say?"
In a very real sense, my first client found me.
In time, that first client and I kept hiring each other back and forth for a bunch of things, until it got to the point where we were just passing $X000 back and forth.
It just got silly, I asked @mike_julian to run my company, and here we are today.