So big pull requests suck, humans suck at repeatable things, open source makes for a fun hobby, and devs are weird.
A bonus fifth item: anything can sound obvious and dumb when I reduce it to something absurd on Twitter.
I assume that at least 20K of those 35,000 organizations are various Microsoft business units.
These numbers likewise drop by 2/3 if you remove my horrifically broken bash script with a loop.
Rust doesn't appear on this graph of popular languages because people don't use @github to store their conference slide decks.
"What would you do if the world was ending?"
Apparently you would go write some JavaScript.
Ideally most of this was to projects that don't explicitly enrich @Elastic and basically nobody else.
Next we talk about Developer Activity. For evaluating this based upon GitHub issues and commits, we sure do spend a lot of fucking time in meetings, don't we...
Busting out a @sarah_edo quote demonstrates that @nicolefv is quite capable of ensuring that you find out, should you be so foolish as to fuck around.
This feels like a @nicolefv throwback to her earlier work wherein she compares the differences between what I recall as "high performing elite teams" and "shitty ones."
Probably the single thing I would change is explicitly calling out that "living through a global pandemic might not be the best productivity experiment" not because the report didn't control for this, but because many managers will take the wrong lesson.
Now let's talk about what this report didn't have.
* A 'give us your contact info' gateway to download it.
* A sales pitch for any one of countless @GitHub, @Azure, or @Microsoft products.
* Anything for me to really dunk on. It's *superbly* well executed.
In summation: @nicolefv is a magical treasure that remains one of the best parts of our industry, and @Github (pronounced "Jith Ubb") is supremely lucky to have her.
I will now take questions and direct them to Dr. Forsgren.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
Congrats to @revue on their @Twitter acquisition. Now, some thoughts on paid newsletters.
Last Week in AWS (lastweekinaws.com) is my snarky email newsletter. I have ~23000 or so subscribers.
There are some folks (Revue is one, @substack is another) that would urge me to write a paid newsletter, to which subscribers are the revenue source.
Unfortunately for my model it's a complete non-starter. Basically none of you you would pay say, $100 a year for my ridiculous ranting nonsense. I might be wrong on that but I seriously doubt it.
Let's go back in time and put on my Analyst / Marketing pants. It's years ago, I'm advising @elastic, and @awscloud has just come out with "Amazon Elasticsearch." This feels bad, since (as attested in court) they didn't give a heads up, and there's the danger of brand confusion.
First, I've gotta admit that I'm fighting a rearguard action in some ways. "Elastic Compute" predates the founding of the company and its trademark by a lot, and there are a bunch of other "Elastic" terms people equate with AWS.
In effect, the odds are basically zero that people already aren't equating our stuff as being an Amazon offering. I'm only half kidding when I suggest "Stretchy-Go-Findy" as an alternate name.
Another day, another "fuck you for paying us" from Google.
If you don’t think sharp edges like this on your consumer products shape opinions of your business (read as: cloud) products, you’re dead wrong.
(This is my “personal” account; it’s my 20 year old vanity domain for personal email; nobody else has an account on the domain. The only way to have a custom domain is to pay Google—which I’m normally okay with until I hit nonsense like this.)