
Festina Lente - @livestoredev contributor - Previously @inngest, @synthesischool - #OD50 Fellow @beondeck
Switzerland
Joined March 2011
- Tweets2.3K
- Following2.3K
- Followers614
- Likes16.8K
I've been reading this page and it's been very pretty hard to grok pnpm.io/npmrc
It feels like it was AI generated with little care.
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.
A shower thought:
Good architecture compounds.
Bad architecture multiplies debt.
In the age of agentic coding, both effects are greatly amplified...
Agents can introduce debt faster than humans can pay it down.
Without addressing the underlying patterns, every increase in output also increases the cleanup required.
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...
















