Recent writing
Why we moved our caching layer from multi-tenant to single-tenant, what that mental model unlocks for latency and operations, and how we're shaping the cache as a leaderless network of nodes that lives close to wherever you happen to be building.
Coding agents are lowering the cost of adopting powerful but complex tools like Kubernetes and Bazel, but I don't think that means we're heading toward a Bazel-everywhere world. The reasons are not technical, they are ecosystem-shaped.
On the round-to-round game, the stories companies tell users to mask enshittification, and why I want to build a company that puts craft and people before growth at any cost.
A rainy Sunday trying Codex made me rethink my terminal-first agent workflow, and made me see a big opportunity for tighter integration with tools like mise and Pitchfork.
We have the data from builds and test runs. We have the agent primitives in Elixir. Now we are connecting them into something that can actively improve your developer workflows, not just report on them.
When the only input your company accepts is through paying customers, you limit your ceiling to a small pool of ideas. Open communities create a different kind of exchange, one that compounds in ways money can't measure.
Cloud development environments keep getting rebranded, but they keep running into the same fundamental problem: your workflow is not portable. Agents might be changing the question entirely.
When your team works with multiple clones of the same repository, global resources like ports and databases start to conflict. Here is how we solved it at Tuist using mise and a simple random suffix.
Coding agents are making developers and organizations less tolerant of slow toolchains. That shift in tolerance is opening a door that was surprisingly hard to open before.
I built Helmsman, an Elixir framework for building LLM-based agents, inspired by Pi's SDK mode and aligned with Elixir patterns and conventions.
Openness is not a trend or a distribution strategy. It's a way of building trust, expanding your pool of ideas, and creating something that lasts.
A bet that obsession matters more than speed. That personality matters more than feature parity. That going deep matters more than going wide.
Tuist started at the toolchain layer and is working its way down to compute and caching. This is the whole house, from roof to foundation, and why going deep into each layer is how you earn trust that money cannot buy.
Developers who build companies tend to fall in love with their creations. That love is a strength, but it can also become a blind spot when others see your work as an asset to acquire rather than a craft to respect.
Coding agents decoupled development from the editor. What follows is a new kind of platform where steering, reviewing, and collaborating on code looks nothing like what we are used to.
Why the future of CI isn't about dedicated compute but about colocated caching, and how build systems, coding agents, and shifting economics are making that future real.
Building a long-term company in dev tooling means accepting that some things can't be rushed. Ideas have their own pace, trust takes time, and not every shortcut is worth taking.
Reflections on how AI is reshaping code production, why companies must rethink where value lives, and what independence means in a world of accelerating change.
A few years ago, Willem, one of the best managers I've had at Shopify, told me something that stuck with me. He said that when everything around you feels broken, it's easy to adopt that tone and let it become chronic. I've been thinking about that lately.
After seeing Moltbot grow rapidly, I became intrigued by bot interactions. This led me to build Clawgram, a photo-first social network for AI agents where bots can post, like, comment, and follow each other.