Recent writing
For as long as we have built SaaS, we assumed a human was the one registering, setting up, and wiring things together. That assumption is quietly breaking, and it changes how software should be designed.
On the people who feel great by making you feel small, the gravitational force of doubt around anyone building something, and why we moved on from one of those conversations today.
A running accident in 2024 injured my sciatic nerve and left me with foot drop. Two years, a nerve graft, and a year and a half of daily mental work later, an electromyography finally showed the brain's signals reaching the muscle again.
Why productivity infrastructure suddenly matters for everyone, not just the giants. Local incrementality no longer holds once coding harnesses spin up parallel worktrees, and build systems need a redesign around distributed incrementality.
A post on X predicted that development would all move to remote sandboxes. Here is why I think that is a mirage, what makes the model attractive to executives and unappealing to developers, and where selling compute actually makes sense.
Daytona went closed source yesterday, and the reasoning was security. Look at these moves through the lens of business instead, and a different and more honest story shows up.
Why we are betting on remote caching instead of compute, and building Kura and Once in the open as the quiet corner everyone else overlooked.
Every build system is a trade-off. The one that interests me is whether you stay native or fork the ecosystem, because a fork has a cost that doesn't go unnoticed.
Coding agents can write the code. The harder part is closing the loop afterwards, and I think the missing piece is an automation graph that connects changes to the work, context, and people they imply.
Selectiveness is the real theme underneath monorepos and the agentic world: a graph of domains and tasks that tells your compute what to actually do.
Caching and remote execution are welded to whoever runs your CI. We need a narrow waist—a common contract for build caching and remote execution that any provider can implement.
A company stitched together from SaaS tools ends up with a fragmented understanding of itself. Agents make that tax impossible to ignore, and make it worth building the graph of the company yourself.
Why renting your cost advantage from the same clouds you compete with leaves you exposed, the difference between a platform and a catalog, and why at Tuist compute is a complement to the cache, not a product.
On tinkering with new ideas, the tension with perfectionism and fear, and building Tuist as a company that keeps pushing the line for what's possible.
A look at the compute market right now, why every CI and runner company is shipping the same terminal-in-the-browser product, and what we are doing instead at Tuist.
Three weeks of cutting instead of patching: moving off Render onto our own Kubernetes cluster on Hetzner, rewriting the cache in Rust as Kura, reconciling bare-metal compute, and why infrastructure that agents can read natively turned into a strategy.
Layoffs are the bill for designing companies in a world that no longer exists. With the cost of building collapsed, small teams can finally design how they want to work first, and shape the tools around that, instead of bending themselves to off-the-shelf opinions.
Build caching is becoming an everyone problem. Here is how we think about productizing it at Tuist for indie developers and small teams, not just enterprises.
I keep coming back to the wave of companies that made infrastructure feel easy, and what coding agents are doing to the layer of convenience they were quietly selling.
Why we are building Atlas at Tuist, an internal platform designed to help a very small team operate with the leverage of a much larger one.