Michael Mignano

7.8K posts

Michael Mignano banner
Michael Mignano

Michael Mignano

@mignano

VC @Lightspeedvp, Co-Founder @OboeLabs, former Co-Founder and CEO of Anchor (acquired by @Spotify). Early investor in @meetgranola @suno @xai @macroscope + more

Katılım Temmuz 2008
700 Takip Edilen32.3K Takipçiler
Sabitlenmiş Tweet
Michael Mignano
Michael Mignano@mignano·
People are underestimating what will happen to software as a result of AI. Most are focused on how it'll make creating software incrementally easier, faster, cheaper. Few are discussing just how vast the universe of software becomes when this happens. We will have 100x more software (at a minimum!) as a result of AI. There will be a gigantic long tail of every type of application you could ever imagine. Most will have few users, if any. But a lot of it will be super niche and customized to very specific use cases. Some huge hits will break out. People who make software (without ever actually knowing how to code) will emerge as "creators". Most of these people will be dismissed by purists for not making "real software". And some of these people will become very wealthy. And an entire ecosystem will spring up around it. Marketplaces, tools, entertainment, media, etc. The same thing that has happened to every other form of media is about to happen to software. It'll look like a joke at first. But then it will be far too big to ignore.
English
194
284
2.5K
361.9K
Preston
Preston@metapreston·
@mignano I agree with that. Mobile is important for beginners and Apple should not stand in the way
English
1
0
1
58
Michael Mignano
Michael Mignano@mignano·
This feels like the wrong time to be enforcing these rules and a very bad strategic decision. We're going through a total renaissance of software development and an explosion of the long tail. There will be more apps than ever before. Builders need an easy way to distribute them. If Apple doesn't let the supply flow to the App Store, the demand will follow it somewhere else.
Stephanie Palazzolo@steph_palazzolo

Apple has been cracking down on popular vibecoding apps like Replit and Vibecode in recent months, saying that such features are in violation of its App Store rules. For more on why this is happening, check out this morning's story from @aatilley and me: theinformation.com/articles/apple…

English
5
0
23
7.4K
Preston
Preston@metapreston·
@mignano There's no real need for apps to be made in existing apps. Making apps on web/desktop fits the power-law use-case of making apps
English
1
0
5
449
Krush
Krush@krushil_a·
@mignano I don’t get how vibe coded apps are violating App Store’s publishing policies
English
1
0
3
105
Michael Mignano
Michael Mignano@mignano·
@chrisargo_ blocking unlawful, dangerous, insecure, etc stuff is obviously a good thing. beyond that i think its up to the customers to decide what quality means, not the platform.
English
0
0
1
42
Chris
Chris@chrisargo_·
@mignano You don’t think that having a quality bar benefits customers?
English
1
0
0
63
Michael Mignano
Michael Mignano@mignano·
@chandlerjward also, in general, i have found the opposite to be true: when you let the longtail publish unfettered (with obviously ugly, unlawful, dangerous stuff being the exception), breakouts emerge.
English
0
0
1
32
Chandler Ward
Chandler Ward@chandlerjward·
Apple can’t keep up with the volume of submissions and re-submissions. The store is getting absolutely flooded with tons of low quality single-feature apps and templated/cloned vibe apps. It’s common practice to purge the supply side of any marketplace to improve the user experience. This is just the first time we have ever seen an excess of supply in software. So I get raising the bar for quality. That said, a ban on Replit is an overly blunt approach.
English
2
0
0
105
Michael Mignano
Michael Mignano@mignano·
@chandlerjward as i understand it, they're making it harder for people to easily create and distribute apps. those people will find other places to do it.
English
0
0
1
61
Sarah Wolf
Sarah Wolf@sarahzorah·
a credit card but instead of cash back you get Claude credits
English
199
280
6.3K
458.9K
Dami Dina
Dami Dina@DamiDina·
@cjpedregal Side note I saw a granola ad on IG last night and really dig your branding
Dami Dina tweet media
English
1
0
14
1.5K
Chris Pedregal
Chris Pedregal@cjpedregal·
There are some tweets out there saying that Granola is trying to lock down access to your data. Tldr; we are actually trying to become more open, not closed. We’re launching a public API next week to complement our MCP. Read on for context. A couple months ago, we noticed that some folks had reversed engineered our local cache so they could access their meeting data. Our cache was not built for this (it can change at any point), so we launched our MCP to serve this need. The MCP gives full access to your notes and transcripts (all time for paid users, time restricted for free users). MCP usage has exploded since launch, so we felt good about it. A week ago, we updated how we store data in our cache and broke the workarounds. This is on us. Stupidly, we thought we had solved these use cases well enough with our MCP. We’ve now learned that while MCPs are great for connecting to tools like Claude or chatGPT, they don’t meet your needs for agents running locally or for data export / pipeline work. So we’re going to fix this for you ASAP. First, we’ll launch a public API next week to make it easier for you to pull your data. Second, we’ll figure out how to make Granola work better for agents running locally. Whether that’s expanding our MCP, launching a CLI, a local API, etc. The industry is moving quickly here, so we’d appreciate your suggestions. We want Granola data to be accessible and useful wherever you need it. Stay tuned.
English
95
40
789
145.2K
Michael Mignano
Michael Mignano@mignano·
@appenz @meetgranola First rule of VC is do no harm. You're costing a startup real business based on a lazy assumption. Do the research first.
Chris Pedregal@cjpedregal

There are some tweets out there saying that Granola is trying to lock down access to your data. Tldr; we are actually trying to become more open, not closed. We’re launching a public API next week to complement our MCP. Read on for context. A couple months ago, we noticed that some folks had reversed engineered our local cache so they could access their meeting data. Our cache was not built for this (it can change at any point), so we launched our MCP to serve this need. The MCP gives full access to your notes and transcripts (all time for paid users, time restricted for free users). MCP usage has exploded since launch, so we felt good about it. A week ago, we updated how we store data in our cache and broke the workarounds. This is on us. Stupidly, we thought we had solved these use cases well enough with our MCP. We’ve now learned that while MCPs are great for connecting to tools like Claude or chatGPT, they don’t meet your needs for agents running locally or for data export / pipeline work. So we’re going to fix this for you ASAP. First, we’ll launch a public API next week to make it easier for you to pull your data. Second, we’ll figure out how to make Granola work better for agents running locally. Whether that’s expanding our MCP, launching a CLI, a local API, etc. The industry is moving quickly here, so we’d appreciate your suggestions. We want Granola data to be accessible and useful wherever you need it. Stay tuned.

English
1
0
8
995
Guido Appenzeller
Sorry to see Granola @meetgranola going closed. They encrypted their local db, no local and no cloud API. In a world where notes are managed by agents, the app now has zero value. Any recommendations for good alternatives? What are you switching to?
English
178
11
632
334.6K
Michael Mignano
Michael Mignano@mignano·
Great move by Chris and the Granola team. And shameful move by a VC trying to slam a startup based on a lazy assumption.
Chris Pedregal@cjpedregal

There are some tweets out there saying that Granola is trying to lock down access to your data. Tldr; we are actually trying to become more open, not closed. We’re launching a public API next week to complement our MCP. Read on for context. A couple months ago, we noticed that some folks had reversed engineered our local cache so they could access their meeting data. Our cache was not built for this (it can change at any point), so we launched our MCP to serve this need. The MCP gives full access to your notes and transcripts (all time for paid users, time restricted for free users). MCP usage has exploded since launch, so we felt good about it. A week ago, we updated how we store data in our cache and broke the workarounds. This is on us. Stupidly, we thought we had solved these use cases well enough with our MCP. We’ve now learned that while MCPs are great for connecting to tools like Claude or chatGPT, they don’t meet your needs for agents running locally or for data export / pipeline work. So we’re going to fix this for you ASAP. First, we’ll launch a public API next week to make it easier for you to pull your data. Second, we’ll figure out how to make Granola work better for agents running locally. Whether that’s expanding our MCP, launching a CLI, a local API, etc. The industry is moving quickly here, so we’d appreciate your suggestions. We want Granola data to be accessible and useful wherever you need it. Stay tuned.

English
2
1
117
43.1K
Michael Mignano
Michael Mignano@mignano·
@FutbolmeAI builds you a comprehensive course that gets you where you need to go but also lets you take detours.
English
0
0
0
39
Carlos Tecnico
Carlos Tecnico@FutbolmeAI·
@mignano Finally someone says it. Probabilistic output ≠ structured learning. What's Oboe's angle?
English
1
0
1
42
Michael Mignano
Michael Mignano@mignano·
LLMs have infinite knowledge but are actually terrible at teaching us things out of the box. Over time, the probabilistic nature of next token prediction degrades the model's ability to get you to your ultimate destination. New Oboe fixes this.
Nir Zicherman@NirZicherman

x.com/i/article/2031…

English
3
1
19
4K
Michael Mignano
Michael Mignano@mignano·
@unable0_ yea. we're going to see some really interesting things happen as a result. we haven't seen people interact with software this way before.
English
0
1
2
43
Kamil Ruczynski
Kamil Ruczynski@unable0_·
100% agree. I’ve been saying this for a while now. it’s especially true for easy-to-start tools like Lovable. the real use case is simply entertainment. they make people feel powerful by giving them the ability to create something they couldn’t before, and it’s genuinely fun to experience that.
English
1
0
1
53
scott belsky
scott belsky@scottbelsky·
admiring the leader/product fit of @nikitabier advancing this platform. - perfect combo of growth instincts + quick iterations before polish - engaging detractors / clearing abusers w/ transparency features - setting bit for how X should be used through his own use product undeniably better, even though I still want a way to use Grok to leverage my years of bookmarks! 🤞🏼
English
17
7
503
48.6K
Michael Mignano
Michael Mignano@mignano·
buckle up. gonna get bumpy.
jack@jack

we're making @blocks smaller today. here's my note to the company. #### today we're making one of the hardest decisions in the history of our company: we're reducing our organization by nearly half, from over 10,000 people to just under 6,000. that means over 4,000 of you are being asked to leave or entering into consultation. i'll be straight about what's happening, why, and what it means for everyone. first off, if you're one of the people affected, you'll receive your salary for 20 weeks + 1 week per year of tenure, equity vested through the end of may, 6 months of health care, your corporate devices, and $5,000 to put toward whatever you need to help you in this transition (if you’re outside the U.S. you’ll receive similar support but exact details are going to vary based on local requirements). i want you to know that before anything else. everyone will be notified today, whether you're being asked to leave, entering consultation, or asked to stay. we're not making this decision because we're in trouble. our business is strong. gross profit continues to grow, we continue to serve more and more customers, and profitability is improving. but something has changed. we're already seeing that the intelligence tools we’re creating and using, paired with smaller and flatter teams, are enabling a new way of working which fundamentally changes what it means to build and run a company. and that's accelerating rapidly. i had two options: cut gradually over months or years as this shift plays out, or be honest about where we are and act on it now. i chose the latter. repeated rounds of cuts are destructive to morale, to focus, and to the trust that customers and shareholders place in our ability to lead. i'd rather take a hard, clear action now and build from a position we believe in than manage a slow reduction of people toward the same outcome. a smaller company also gives us the space to grow our business the right way, on our own terms, instead of constantly reacting to market pressures. a decision at this scale carries risk. but so does standing still. we've done a full review to determine the roles and people we require to reliably grow the business from here, and we've pressure-tested those decisions from multiple angles. i accept that we may have gotten some of them wrong, and we've built in flexibility to account for that, and do the right thing for our customers. we're not going to just disappear people from slack and email and pretend they were never here. communication channels will stay open through thursday evening (pacific) so everyone can say goodbye properly, and share whatever you wish. i'll also be hosting a live video session to thank everyone at 3:35pm pacific. i know doing it this way might feel awkward. i'd rather it feel awkward and human than efficient and cold. to those of you leaving…i’m grateful for you, and i’m sorry to put you through this. you built what this company is today. that's a fact that i'll honor forever. this decision is not a reflection of what you contributed. you will be a great contributor to any organization going forward. to those staying…i made this decision, and i'll own it. what i'm asking of you is to build with me. we're going to build this company with intelligence at the core of everything we do. how we work, how we create, how we serve our customers. our customers will feel this shift too, and we're going to help them navigate it: towards a future where they can build their own features directly, composed of our capabilities and served through our interfaces. that's what i'm focused on now. expect a note from me tomorrow. jack

English
1
0
32
7.5K