
Festina Lente - @livestoredev contributor - Previously @inngest, @synthesischool - #OD50 Fellow @beondeck
Switzerland
Joined March 2011
- Tweets2.3K
- Following2.3K
- Followers613
- Likes16.8K
convergence to the mean
when everyone looks at everyone else to decide what to make, we eventually stop making anything of our own.
we copy what works. borrow the language, the aesthetic, the features. we call it learning from the market, following best practices, staying competitive. together, everything starts to feel familiar. polished, interchangeable. nothing wrong. nothing alive.
the mean isn’t necessarily bad. it’s where everything lands when we remove the reasons for it to be different.
numbers are easier to compare than feelings, so we make things that produce numbers. we study what gets attention, then shape ourselves around it. eventually the feedback stops informing the work and starts authoring it. we’re no longer asking what we want to say. we’re asking what will be rewarded for saying.
ai makes this loop frictionless. it can draw from more references than we could see in a lifetime. but access to every perspective isn’t the same as having one. it hasn’t lived a particular life that makes one detail unbearable and another beautiful. when we ask it to choose for us without bringing any intention of our own, we get something plausible, easy to approve.
then we ship it, measure it, copy it, and feed it back into the next round. a tidal wave of mid.
this changes not just the work, but the people making it.
we describe ourselves in categories platforms can distribute and markets understand. designer. founder. creator. pick a niche. build a brand. be consistent. the parts that don’t fit become inconvenient, even when those contradictions might produce our most interesting work. we become easier to classify and harder to tell apart.
i think we need to approach making things more like artists.
an artist develops a perspective through the work. making, noticing, choosing, failing, returning. learning what matters even when nobody else cares. craft gives that perspective a form precise enough for someone else to experience.
the life outside the work matters too. the places you’ve lived, the people you’ve loved, the things you’re embarrassed to care about. these aren’t distractions from having something to say. they’re how you come to have something to say.
we understand this with music, paintings, photographs, movies. we expect a person to be present in the choices. we want to experience something we wouldn’t have encountered without them.
software can do this too.
a piece of software expresses beliefs about how life should feel. what deserves your attention. what you should be free to change. whether a task should feel like paperwork or play. even a small interaction can carry someone’s care, humor, or curiosity.
but we rarely talk about software as a medium. we talk about it as an industry. markets to capture, workflows to optimize, competitors to catch up with. we add a feature because someone else has it, without asking whether it belongs. products accumulate the same parts and lose what made them worth choosing.
underneath the branding, it’s all the same thing.
artists learn from others too. the question is whether you’re absorbing those influences into a point of view, or using them to avoid developing one.
what are you trying to let someone feel, understand, or do? why this particular shape? what have you noticed that the existing tools don’t seem to notice?
those questions don’t have answers you can borrow from a competitor’s roadmap.
if we can make almost anything, deciding what deserves to exist becomes more important, not less. speed gives us more chances to exercise judgment. it doesn’t remove the responsibility.
i don’t want a world where every person becomes a more efficient distributor of the same ideas. i want people to use these tools to go further into what they actually care about. to make things specific enough that we can feel someone behind them.
what is the point of everyone being able to make something, if we all end up making the same thing?
Igor Gassmann retweeted
We didn't become builders because we want more output, but to make something good.
To keep make something good, the learning for is needed as much the product you build.
Linear CEO @karrisaarinen: "Making products produces two things: the product, and the learning.
The effort you put into building and designing things teaches you something about what the problem is, what the customers want.
We're in this time now that there's this danger of losing that direct connection with the learning."
Igor Gassmann retweeted
Frantically fixing a confusing product caused by frantic shipping is just more of the same.
Pause and step back. Get the team clear on what you’re building and why. Have clarity to guide the shape, what ships and what doesn’t.
Quality is a way of working, not a cleanup sprint.
Igor Gassmann retweeted
Effect v4 is here.
One ecosystem. Zero dependencies.
The next chapter of Effect and the foundation for building reliable software and AI agents in TypeScript.
13 years ago, Apple asked a question that hits me harder today than ever:
If everyone is busy making everything, how can anyone perfect anything?
Every day, I see a world flooded with effortless AI slops. I’m realizing that to build something truly great today, you need a level of focus the world has never demanded before.
It feels like trying to write a quiet, beautiful song in a room full of loud noise.
Igor Gassmann retweeted
one of the biggest gripes i have about tech (and startups) right now is... everyones trying to build the-everything-solution
what i mean is: many startups should be building "features" that can slot in, maybe break out one day. say take all the components you need to make a coding agent work: the IDE, verification layers, sandboxes/vms, security, etc.
but instead they're not doing that, and thus no one is achieving any breakout success. they're all just me-toos that dont work that well, and certainly not better than the other persons idea
i dont really blame them as you are taught to swing big, and you're somewhat naively convinced you can right now. except whats happening is everyones blindly confident that they've found _the secret sauce_ (100% placebo btw) and they barely ever scratch the surface
on average I'd agree with the wisdom that you should aim big, avoid being the feature, but this is an odd domain where the problems - each component - is so uncommonly difficult and valuable that we SHOULD be building those. and thats just in software dev!
you see the same thing in how indie developers operate, and in open source, where instead of trying to lego together things to (truly) solve a really big problem, everyones pretending they can vibe code some slop
with the way its going we're like six months away from people thinking SQL is too complicated and having their agents invent new graph stores...
Igor Gassmann retweeted
gave up on waiting on nikita for the articles fix - part 1 is here part 2 is coming
Igor Gassmann retweeted

Shannon Sands@max_paperclipsJul 16
Australia
AustraliaConnected via Australia Android AppAccount-level information, not a live location or per-post device.
this is like when divorced mum & dad fight for the kids affections by giving them endless treats
ClaudeDevs@ClaudeDevsJul 16United States
United StatesConnected via WebAccount-level information, not a live location or per-post device.
We've reset 5-hour and weekly rate limits for all users.
Igor Gassmann retweeted
Like this but understanding what your code is doing
Igor Gassmann retweeted
difference between cloudflare vs vercel (ignoring cost, purely on product quality):
we use cloudflare extensively and pay thousands of dollars every month, so I'm obviously a BIG BIG FAN of everything they do. But just think about it
Both are doing everything (general AI cloud). but when vercel does it, they do it with utmost taste, obsession, and thoughtfulness. There's almost never a hiccup, missed doc, question or error in the way.
When cloudflare does it, it's cool - Awesome concept. Not 100% at its potential yet, the product might as well not be maintained in a few months. But it exists today.
Technically cloudflare has the opportunity to build a vercel (early obsession around devplat), a turbopuffer (better Vectorize), a browserbase (better browser rendering), maybe even a together AI (workers AI++), Openrouter (AI Gateway ++), Resend (Email sending ++), Blacksmith (FAST and cheap builds++). even Supermemory (better AI memory product?) But they won't, they can't.
And this is only accounting for a small section of the stuff they already have. I'm sure all the products drive a lot of revenue, I'm not concerned about that as a user. I'm concerned about my experience. imagine how big of a generational difference it makes to make the best product for that particular industry.
I gotta give it to vercel for nailing everything they build. v0 is legit top tier, AI sdk is a top AI framework. NextJS is the biggest web framework. Workflows has a beautiful DX, their gateway is really good, too. They did a fantastic job with fluid compute. Kinda feels like magic
It's clear that vercel is super obsessed and driven towards specific goals, and when they do something, they do it really really well. It's a pleasure to see them execute.
Just like Cognition did, Vercel could one day do an ad saying "Remember vercel? It's not expensive anymore" and could just win the market. (I'm not even sure if it really is expensive. My judgement is years old at this point)
Today I spent like 4-5 hours trying to do something really simple with cloudflare (a preview deployment. that's it) and was unsuccessful, rage quit and felt like shit, felt super tired and burnt out. like it ruined the entire day. All this while I couldn't stop but wonder: What would be the experience on Vercel? how would it feel? Is all this pain worth it?
Also insane that I encounter these scenarios despite working there for more than a year and having full access to everyone there for any help I need. I cannot imagine the experience for people just getting started / learning about cloudflare.
It is also very clear that Cloudflare is executing too! The dashboard is improving a lot, the products are getting better. But not 100% there - This is why I've invested a LOT in cloudflare personally (both mentally and monetarily) and I believe in them.
At the same time as a founder + builder, it's fascinating to see a company kill it at the scale Vercel does tbh. @rauchg is inspirational!
Igor Gassmann retweeted
Replying to @Nicolas_Colin
I think the pity and mockery stems from so many Europeans (usually institutions/"experts") dismissing AC's utility. The vast majority of the debate is not over the mechanics and logistics of deployment, but whether widespread AC is in principle desirable in the first place. I think it garners so much attention from Americans (and Europeans such as myself) because it's a vivid distillation of the self-destructive "degrowth" hysteria that is so prevalent and harmful in many European policy matters. It is the same impulse that led to Germany decommissioning its nuclear capacity, and it is a substantial contributor to the broader economic challenges of the continent.
Igor Gassmann retweeted
Today on Effect Office Hours, we’re talking @rivet_dev with @NathanFlurry and @igassmann.
Join the livestream at 10:00 AM ET / 16:00 CET
youtube.com/live/d__H7pJWOnk…
Igor Gassmann retweeted
Feels like we're all just building "things for building other things" and not a lot of "things" anymore.
Igor Gassmann retweeted
If you write @EffectTS_ for agents or realtime, we've been cooking:
Effect gives you incredible primitives for stateful apps, but they live and die with one process.
Now with the Rivet SDK, your Effect code can run as a Rivet Actor: a long-running, lightweight process.
Igor Gassmann retweeted
I have not tried this yet but it looks great, one of the most involved and non trivial integrations to date! Props to River and @igassmann for the work on this
If you write @EffectTS_ for agents or realtime, we've been cooking:
Effect gives you incredible primitives for stateful apps, but they live and die with one process.
Now with the Rivet SDK, your Effect code can run as a Rivet Actor: a long-running, lightweight process.




























