anshublog

6 ms·

1.
Models have no business models(twitter.com)
3 points by anshublog 2mo ago|2 comments
2.
by anshublog 2mo ago
Models inherently lack a business model so they need to find one. They have monster cap tables and firepower but lack a durable core revenue engine. This leads them to go up and down the stack - cloud, api, coding, chips, devices, ad revenu
3.
by anshublog 8mo ago
NVIDIA was a small cap in 2016. Netflix was a small cap in 2016. Intel was the leader. Comcast was the leader. Yes Google and Apple have done great but its because they have made some good strategic decisions. And some (not all) of their fa
4.
by anshublog 8mo ago
thanks. :) [og author here]
5.
by anshublog 8mo ago
Yes, when I wrote this article - I was pointing out that we seem to have missed this rather common pattern. And if you understand this pattern you can avoid some strategy mistakes. I didn't claim that this one pattern explains all of t
6.
by anshublog 8mo ago
exactly. it took longer for Apple to fix its Maps app - and to this day their email app is nowhere as good as most third party apps. Even iMessage is lacking features that WhatsApp and Signal built 5 years ago. (And iMessage is clearly thei
7.
by anshublog 8mo ago
this whole thread is hilarious and yet quite insightful. Yes, the core idea behind Stack Fallacy was that if you are Apple you don't need to build a better CPU than Intel for all workloads - you just need M3 for your Mac. So yes - just
8.
by anshublog 8mo ago
Love the name. I wish I had called it Sandwich fallacy instead. (I am the author.)
9.
by anshublog 8mo ago
Oh wow - interesting to see this up again. I am the author of The Stack Fallacy. #AMA I am now founder of Skyflow, we are runtime AI data security platform. This is my third startup, and previously I ran strategy for Salesforce.
10.
by anshublog 4y ago
This is sad. This was avoidable. There’s no recession as far as the eye can see. There’s a crypto recession. Let’s go back to building real tech.
11.
by anshublog 5y ago
By that definition, everything is a trillion dollar market. :)
12.
by anshublog 5y ago
I have seen fully encrypted end to end flows to Twilio. You got it 99% right here. (There's some nuance around re-encryption proxies and how that is handled.)
13.
by anshublog 5y ago
@xori, homomorphic has scale challenges. curious what you think of it and have you seen it in production? also, have you heard of polymorphic? (BYOK is an extremely important feature for this category.)
14.
by anshublog 5y ago
I am founder & CEO of Skyflow PII data privacy vault. We are vaguely similar but our product line is focused on offering "PII database as a service" - and not really relays and cages. Happy to answer any questions. To answer y
15.
by anshublog 5y ago
How do you build a business in the shadow of AWS, GCP, and Azure as a startup? How do you find the white spaces? What areas have they over/under invested in? What other startups are doing in those spaces? Greylock spent months investig
16.
Mapping the 3 big Clouds: Castles in the Cloud(greylock.com)
15 points by anshublog 5y ago|7 comments
17.
by anshublog 5y ago
I will happily pay $30/month for Mighty. The browser is literally where I spent 100% of my time. The pattern of hosted/virtualized browsers is well understood for over a decade but mostly built and delivered poorly for the low end
18.
by anshublog 7y ago
"Ever since I left Facebook board, I have become convinced its the new diabetes." (Ok, I wrote that.)
19.
by anshublog 11y ago
"I guess my takeaway is that the companies can in fact take these arenas, but they underestimate the challenge." Yes. And their core mistake is not understanding the real needs of the customer because they make assumptions in a fa
20.
by anshublog 11y ago
agreed. Its just hard to have title that says "Why some companies fail repeatedly". All of us are competing with "17 people under 30"... listicles.
21.
by anshublog 11y ago
I am the author. Happy to answer any questions about my post.
22.
by anshublog 11y ago
This is exactly what I (writer of the article) wanted to communicate. I wish I had said it as clearly. I agree with you on the problem with moving up. Not so sure about the gradual move up. Another path is to acquire and let them lead. Anot
23.
by anshublog 11y ago
I (author) didn't say it's hard to move up from (only) engineering side. It's hard to move up from customer empathy perspective. Hence the emphasis on what to build. It's a product strategy question.
24.
by anshublog 11y ago
Yes many open source projects suffer from this too. We as engineers (even former ones) often assume the what to build is "obvious". This is often not true, if ever. The best open source projects are ones where engineers are the en
25.
by anshublog 11y ago
They think they know their competencies (database systems in one case, virtualization in another) but often they misunderstand what customers really value up the stack - in this example, Workday customers really don't care if it runs O
26.
by anshublog 11y ago
Exactly. When you go down the stack like Amazon did with AWS, you know your customer (often you). You also know the key pain points and gaps in the market. This is especially so in "as a service" markets.
27.
by anshublog 12y ago
Me likes iOS. It seems to be the easiest for me to understand.
28.
by anshublog 13y ago
There are 32 from Indian Institutes of Technology. (But the data is under various names.) IITs (acronym) are unique because its a really small system - graduating 2500 students across all 5 IITs in 1996 for example. Would be one of the few