CEOs interviewing other CEOs, Public Dating Shows, @sriramk + @aarthir becoming the next great show hosts.

I cannot read 2 tweets without seeing something on Clubhouse. A new room, a thread on Elon, a bull case on their $1B eval.

Let’s take a look at the rise of Clubhouse.

As part of our commitment to keeping our customers/community protected & informed, we are releasing a blog that shines light on transition between Stage 1 and 2 of #Solorigate/#SUNBURST campaign, custom Cobalt Strike loaders, post-exploit. artifacts, IOCs: https://t.co/b0ReHMa63u

Here are some highlights:
The missing link between the Solorigate backdoor and the custom #CobaltStrike loaders observed during the #Solorigate is an Image File Execution Options (IFEO) Debugger registry value created for the legitimate process dllhost.exe (ATT&CK ID: T1546.012).

Once the registry value is created, the attackers wait for the occasional execution of dllhost.exe, which might happen naturally on a system. This execution triggers a process launch of wscript.exe configured to run the VBScript file dropped by the SolarWinds backdoor (Stage 1).

The VBScript in turn runs rundll32.exe, activating the Cobalt Strike loader DLL using a clean parent/child process tree completely disconnected from the SolarWinds process. Finally, the VBScript removes the previously created IFEO value to clean up any traces of execution.

On the custom Cobalt Strike Loaders: we identified several second-stage malware, including TEARDROP, Raindrop, and other custom loaders for the Cobalt Strike beacon. During the lateral movement phase, the custom loader DLLs are dropped mostly in existing Windows sub-directories.

While many Amazon warehouse workers in Europe have unionized, its brutalized, underpaid, routinely maimed US workforce remains tragically unorganized, thanks to the US's weak labor laws that make forming a union far harder than at any time since the Gilded Age.

1/

But all that may be about to change: 6000 warehouse workers in #BHM1, the massive Amazon warehouse in Bessemer, AL, will vote next month on a push to unionize under the

Amazon, like other tech giants, is absolutely reliant on building and maintaining a competitive advantage by exploiting technology to drive wages ever downward while ducking responsibility for harming workers.

3/

Big Tech is pants-wettingly afraid of unionization, and that goes double for any solidarity between high-paid tech workers and misclassified/outsourced warehouse workers and other "unskilled" laborers.

4/

Amazon has gone so far as to hire the Pinkertons, renowned as some of history's most violent anti-worker terrorists, to bust unionization drives in its

It's endlessly fascinating how economic datapoints get interpreted.

When I was in charge of a P&L, the guy who ran Finance for us and I had what we called the 'shelf plan.'

There were maybe 3-4 of us who knew it existed.

What's a shelf plan?
1/

Well it's a plan you keep on the shelf (full FP&A model), that you hope you never have to use.

It reduces forward hires, cuts back various line items (typically ad spend, travel, that sort of thing).

Oh, it also has a big fat RIF in there.

That's why we don't talk about it.
2/

Why have a plan instead of winging it?

Because this is where companies (particularly young companies) sometimes err. They do little cuts - 2-3% here and there, preserving as much headcount as they can, that sort of thing.

This is incorrect.
3/

If you're at the point where you need to make material changes to your forward P&L, at 2-3% RIF will be followed by another.

And another.

And this series of progressive cuts will cripple morale, incrementally reducing the productivity of the staff you retain to survive.
4/

And so the shelf plan cuts deep.

Your goal is to go from being a peacetime machine to a wartime machine, so you gotta lean out quick. Can't do that without a plan, hence the need to have one.

~30% cut is what you need.

And then you need to tell everyone left they're safe.
5/

If you’re a Startup trying to compete with a Megacorp—the 800-pound Gorilla in the space—you need to understand the tax inherent to being a Gorilla

And then you need to make that tax work against the Gorilla—with your product's positioning & features

A thread on Gorilla taxes👇🏾

1/
Collaboration Tax

Getting two or more product groups at a megacorp to collaborate on creating a seamless end user experience is the hardest problem in computer science.

(I am not joking)

Examples of Collaboration Tax:

Calendly exists because the Gmail team & Calendar team haven’t worked together on creating a more seamless experience for that use case.

Loom might succeed because the Gmail, Video, Meet teams at Google are probably too busy with their own goals.

The takeaway for startups:

If you can create meaningful value by seamlessly integrating features of two or more distinct Gorilla products, you will typically have a lot of runway before the Gorilla can get its act together and eliminate its Collaboration Tax.

2/
Denominator Tax

Once a Gorilla’s product reaches massive scale (i.e. the denominator for its metrics gets very large), the pressure of OKRs & incentives will often force the Gorilla’s product teams to prioritize breadth of usage more than depth of usage.