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.
Absolutely no one sensible is going to read that thread and say "I will absolutely not give ACG my business."
But how many people will read about ACG for the first time and look into the company further?
What do you think the point of the report was in the first place?
Still think I'm being unfair? Try this one on for size:
These reports and keynotes I mock? I'm usually explicitly invited to do so by the company in question.
All three tier 1 cloud vendors have expressly invited me to their conferences to livetweet the keynotes.
Very often this *does* become an analyst engagement, because the questions that flow naturally are "you're right, there are some problems with the report. How do we do a better job with the next one?"
I have many thoughts on that.
If I thought for a second that @forrestbrazeal or the rest of the @acloudguru team was actually upset at my teardown I'd be apologizing profusely. You don't make people feel shitty, full stop.
There are levels to the humor, and I invariably hide insight inside of it, mostly because it amuses me.
It's very much *not* purely shitposting without a deeper perspective.
Because most people suck at doing it. Remember, the failure mode of "clever" is "asshole." It's being mean for the sake of being mean, without any redeeming value to it.
“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.
"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.
"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.