@lloyd

Scratched it ✅

I'm all for pricing AI activities per "outcome" and think that is an attractive proposition. I also think it's very difficult to get customers to define that outcome clearly enough that it is possible to achieve.

IMO the industry will conclude that price per activity is how we're pricing AI

Who decided that 🌶️ this was going to be called "hot pepper" and not "chili". I never find it first try!

think this is a case of there being a gap in the market for Arc... but no market in the gap

did you ever try SigmaOS? I liked that too

Got a new iPhone today. It’s nice hardware, sure. I’m most impressed with the transfer from my old phone - almost everything is already logged in, works as expected. So smooth!

hmm maybe

sometimes I want to enforce an aspect ratio?

yeah, exactly. my pet peeve would be horizontal lines. then you drop _another_ component in that has it's own margin and get it doubled up and looks a bit off - here for example

Supabase is sweet. Very easy to get to grips with + handles all the Auth stuff in a clever way ("RLS") too, which I find a little too scary to roll my own. Runs locally too.

Also has a nice web dashboard, "branch splitting" etc. so migrations are less scary.

database.new :-)

What are you building on top of? Supabase?

random thoughts
1. people struggle to compose so the content has margins but any lines reach edge to edge and ignore them
2. I expect them to re-arrange predictably at different breakpoints
3. I want them to be somewhat consistent "card sizes" for predictable layout

Yeah boiiiii! Having fun?

I guess I haven't quite expanded outside of Designer bsky yet 👀

Pretty interesting breakdown on Postgres performance over time

vondra.me/posts/postgr...

We have it, but only because it is such a compelling differentiator that you're logged in as YOU and not some random terminal shared by a team. I point it out during demos etc. If it's intrinsically single player I'm not much of a fan, feels fluffy

Oh man you're so right. Beige feed

for sure - there aren't details to sweat if you're dead ☠️

Love this idea. It is often a struggle to get these things feeling right without landing on some library default

Agreed. I also think it's kinda impossible to teach? You just have to mess it up and feel the pain of putting your fingers in your ears a few times

we finally bullied Bo into becoming a Designer Who Codes™️

If you really understand what you're trying to build, you can't help but be in the details. You see how this "tiny thing" creates friction that compounds into problems for your users and goals.

Eliminating that friction compounds too

When I think about the tools I really like - Linear for example - it's clear the creators sweat the details. It's strange to me that it's conventional wisdom that you shouldn't really do that?

Project Hail Mary
Artemis
Ed by qntm
Mickey7
3 body problem
Enders Game

👀