211–220 of 277 posts
Earlier quoted context omitted.
If F => M then doesn't G => A? Which is good, we don't want to have to go around calling them MAGNA!
Every one of the Facebook companies is a household name with hundreds of millions of users. The same cannot be said for the Alphabet companies aside from Google.
Earlier quoted context omitted.
He shared his dev setup at Dev Tool Time ( https://srcgr.ph/mitchell-hashimoto ) which shows how passionate he is about engineering. Going from CEO -> CTO -> IC solidifies his genuineness.
TBH what I got out of this is that he’s got a simple solid setup that works for him. He clearly doesn’t burn time changing his setup often and that makes sense.
Holly mother of God. Mitchell was still on HN yesterday, as he was replying something about Backblaze IPO and its business. Today it is his IPO, $259 million revenue. 2100+ Customers, 1500+ employees, $10 Billion Valuation......... I mean I felt it wasn't that long ago Vagrant was "the" tool for the job. How it all started, the submission on HN [1], quote: > This project has been the love child of myself and John Ben…
If that’s $260M pa for 1500 employees then that works out as $40k revenue per employee per quarter. Compare with APPL and FB doing [correction: over $600k] per employee per quarter. Not a value judgment. But I only recently started noticing these numbers and it really puts the big players’ spending power into perspective. Hiring engineers away from FAANG is incredibly expensive. Edit: thanks for the corrections in th…
HEY LOOK, IT'S A PARADE, I'M GOING TO GO RAIN ON IT!
"Hey so I joined the high school wrestling team." OH YEAH WELL I BET YOU CAN'T BEAT UP HULK HOGAN.
Earlier quoted context omitted.
Agree! Here's a recent video of Mitchell at Dev Tool Time proving your statement: https://srcgr.ph/mitchell-hashimoto
Wow, that's a pretty similar setup I'm looking at making in the next couple months. Thanks for the link.
Earlier quoted context omitted.
Given recent name changes, MAANG works, but it can be MANGA or MAGNA now. I like "MAGNAM" if you include Microsoft.
I can’t believe there was a time where Microsoft wasn’t considered as big of a tech company as Netflix.
Earlier quoted context omitted.
He shared his dev setup at Dev Tool Time ( https://srcgr.ph/mitchell-hashimoto ) which shows how passionate he is about engineering. Going from CEO -> CTO -> IC solidifies his genuineness.
TBH what I got out of this is that he’s got a simple solid setup that works for him. He clearly doesn’t burn time changing his setup often and that makes sense.
Earlier quoted context omitted.
The economy of scale - at FAANG(MAANG?) scale you can have extremely efficient money making features that only takes a few engineer to support thousands. For things that are completely software, it does not surprise me that millions per employee in earnings is realized - that's just what happens when you operate at that scale. And that's accounting for all of the overhead in personnel that scale entails.
True. The number of engineers is not linearly correlated with the number of customers, but the number of features. If you have a relatively simple product and you can somehow still compete (niche market, patents etc), you can get away with a very low head count. WhatsApp famously had only 35 engineers and ~450M users when Facebook acquired them.
Even then, they can still be insanely profitable per engineer.
Earlier quoted context omitted.
“People should use Kubernetes instead” is an interesting take considering your first paragraph. :) You’ve perhaps not had to troubleshooting issues in a more advanced k8s setup - that is something that is not “for most people”. Keeping services discoverable, with service health-checks and configuration data at hand in the k/v is not needed in the “cloud”? I guess a lot comes down to how you opt to manage you services…
What I am saying is that Kubernetes has become the mainstream tool to use. You have to put up good reasons or custom needs to use something else. A thing I like about Consul is that you can also use it as a KV. Something I lack in the cloud. The Vault in Azure is the Keyvault which is all around terrible but Keyvault in conjunction with how Azure works in general is sufficient to build secure infrastructure.
Its bloody too complex was a good enough reason to move off it to ECS.