
Growth engineer at @supabase. Making small apps on nights and weekends.
San Francisco, CA
Joined January 2007
- Tweets13.5K
- Following1.7K
- Followers2.6K
- Likes14.5K
Sean Oliver retweeted
My god this is such a good speech that every SWE needs to hear. You know what? Every person should hear it
Keep the happy memories, eyes on the reality, be excited about the future. That’s the best that anyone can do
Sean Oliver retweeted
I now mostly use the Instacart UI to review shopping carts that Muse has filled for me. I'd like to be able to speak my feedback to muse while I look at the contents, watching them update as muse makes changes and occasionally tweaking by hand when it’s easier.
I want UIs like this for everything: surfaces designed from scratch for collaborating with an agent to get things done together without giving up control over the output.
The interesting question here is who will build this. Presumably there is someone at Instacart working on an Instacart Agent right now, but I don't want to juggle a bunch of purpose-built specific-thing-agents. I want one assistant that can do everything for me. It seems obvious that this form factor will win.
Meta could probably build a great UI for grocery shopping with Muse, but do they actually want to rebuild all of Instacart's business? Eventually, maybe, but in the meantime they'll face competitive pressure from other assistants that do a better job of integrating with Instacart.
This suggests there's some optimal partnership boundary between companies building brains, like meta, and companies building hands, like Instacart. On one side, the brains with the largest number of hands will win, and the other, the hands that work with the largest number of brains will win.
If this is right, it seems like a dynamic that will favor incumbents on both sides on of the brain/hand divide.
Sean Oliver retweeted
another one!!
instacart 🤝 muse
this integration will make it really easy to get all your groceries using muse, and ensure you and your family are always prepared 🥕
Instacart@InstacartSep 22United States
United StatesConnected via WebAccount-level information, not a live location or per-post device.
Instacart is coming to @Muse! Soon, you can connect Instacart, say “Taco Tuesday,” and turn the idea into a cart from your favorite store. Then check out and get groceries delivered to your door. Same Instacart grocery experience, new way to get started. tr.ee/6xWsKG
Sean Oliver retweeted
Introducing Claude Opus 5.5, the first model in our new Claude 5.5 family.
It performs at the level of Claude Fable 5.1 for most tasks, and costs 40% less to run than Opus 5.
Sean Oliver retweeted
Replying to @typesafeai
@typesafeai Jev is FREAKING SICK!!
Playing around with it to create an experimental RLS Linter for @supabase.
You can check it out here: rls-jev-tester.vercel.app/ or view the demo 📺
Sean Oliver retweeted
Can't wait for Supabase Select. October 2nd in San Francisco. Register at select.supabase.com.
Sean Oliver retweeted
Muse for Mac is out today! It works across apps, files, calendar, notes, and messages on your computer. You control what it can access. The team is shipping fast. Download at ai.meta.com/muse/download
Sean Oliver retweeted
speakers for Supabase Select - Oct 2nd at YC
one more to be announced. Get tickets here:
select.supabase.com
Sean Oliver retweeted

Mitchell Hashimoto@mitchellhJul 30
United States
United StatesConnected via United States App StoreAccount-level information, not a live location or per-post device.
Let's talk a bit about what makes the Superlogical multiplexer different architecturally from traditional terminal multiplexers! There's a lot (a LOT) more coming, but wanted to share a little bit about the terminal-specific part compared to tmux and zellij.
Sean Oliver retweeted
Finally, sudo make me a sandwich is reality.
Sean Oliver retweeted
📣 The moment is here. 📣
TypeScript 7 is officially released! 7️⃣
devblogs.microsoft.com/types…
Sean Oliver retweeted
Supabase has raised $500M at a $10B valuation
In this round we are giving @supabase employees the opportunity to cash out 25% of their vested options. We have done this in every round since inception.
We do it as a “cashless transaction” so that employees don’t need to front any cash to exercise their options. This is the friendliest way we could design it until we can offer RSUs.
On top of that, we give employees a 10 year exercise window: whether they stay or leave the company. The typical/default window is 3 months. IMO, equity is earned and employees shouldn't be penalized because they don't have the cash to exercise within 3 months of leaving a job (often that's the time they need the cash/certainty the most).
beautiful tech stack writeup, one of the best i've ever seen in my career.
I always advocate that devtools companies write these up, because it fulfils multiple purposes:
- tell users the care that goes into the product
- tell hires that there's SOTA work here
- tell competitors to give up
- gives back to community
- (nuanced) tell non-fits why they can't have what they want when they think it's an easy request
few actually do this mostly because they don't actually have sufficient depth, or aren't sufficiently good at notetaking/systematic about problemsolving ('its just vibes' or 'honestly we just went with the first thing that worked' doesn't come across as well, so rather not say anything)
so when you've done the work, show the work.
bravo Raycast
One app, two platforms, four programming languages.
The things that look the simplest are often the hardest to build. @raycast is one of them.
Here's a technical deep dive on how we built v2 👉 ray.so/v2-deep-dive
Raycast 2 is built on React?!
Been using Raycast 2.0 for a few days and its noticeably very snappy
Today I was shocked to see they have built it with Web Views and a Node.js backend. You know I had to crack it open.
Light native wrapper. Rust where it matters. No electron of Tauri.
Sean Oliver retweeted
Você sabia que, embora o destino seja o mesmo, a trajetória para chegar até lá evoluiu muito? No vídeo, podemos ver a diferença visual entre as estratégias de voo:
• Apollo 8 (1968): A primeira missão tripulada a orbitar a Lua utilizou uma trajetória de aproximação direta para entrar em órbita lunar. A nave permaneceu relativamente próxima da superfície, em uma órbita baixa, ajudando a preparar o caminho para os pousos que viriam depois.
• Artemis I (2022): Já a missão Artemis utilizou uma Órbita Retrógrada Distante (DRO). Como mostra o gráfico, a nave Orion viajou muito mais longe da Lua, testando os limites de distância para missões tripuladas e aproveitando uma órbita gravitacionalmente estável, ideal para missões de longa duração.
Essas trajetórias não são apenas desenhos no espaço; elas representam um salto tecnológico. Saímos de missões de exploração mais curtas para a preparação de uma presença sustentável na Lua com o Programa Artemis.
Qual dessas trajetórias você achou mais impressionante: a precisão da Apollo ou a amplitude da Artemis?





























