CEO @tuistdev Build software faster Ex @shopify, @soundcloud
Berlin
Joined September 2008
- Tweets4.4K
- Following887
- Followers7.5K
- Likes8.3K
totally agree with marc. people ask me why not swift on android or kotlin on apple platforms. it's not natural.
for shared logic, pick a language whose incentives are to go everywhere. i think apps collapse into rust for the logic, with a thin swift and kotlin layer for ui
prux.org/posts/goodbye-swift…
development is becoming portable. agents do the work, your laptop is just one place you happen to check on it.
i think we should invest in figuring out that portability, and in what role mobile devices play in it
breadth and depth for whole orgs, whatever they build with. becoming the compute backend of user-facing solutions is the obvious move. we're already thinking past it 👀
isn't it beautiful that we have so many build toolchains? @asmitbm has been cooking icons for them in the dashboard, and one of them is new around here… can you spot it? 👀
previews should just be the distribution layer for whatever your build system produces
anyone up for trying a build system with the modern stuff built in, without migrating your project? replies or dms open
a build doesn't end at the binary. it ends with something people or agents can use: an app, a cli, a site, some data
so artifacts are now part of the contract. once describes and publishes them, infra providers decide how they get distributed
github.com/tuist/once/pull/3…
alerts about flaky tests is amazing. next up is auto-fixing them for you, so your test suite remains forever healthy
we're getting there.
with our own compute, i can finally close the loop on how we want to work at tuist: signal-scoped threads, access to macos & linux envs, bring your own subscription, and of course a mobile app with voice as an interface.
native app, built with once, rust at the core, and building fast with @tuistdev 💜
i can't wait for us to move past skills.
they made sense while models didn't know enough. now that knowledge is collapsing into the model, so you need fewer clis, fewer skills, fewer wrappers.
i'm building apps and shipping them to testflight with just apple's apis and curl. the agent doesn't need much else 💜
ojalá lleguemos a tener un reporte de esos sistemas, de su mantenimiento, porque detrás de ellos también hay contratos multi-millonarios...
eldiario.es/castilla-la-manc…
there's a couple of things @1Password should not fail at; being secure, and being fast; but terribly fail at the second, which makes it extremely annoying to use.
Pedro Piñera retweeted
is your test suite the slowest step in ci? split it across balanced shards so every machine finishes at about the same time
tuist.dev/blog/2026/03/25/te…
every "my builds are slow" thread gets the same reply: convert. no questions about the project, the team, or the toolchain. just convert
no se habla de esto lo suficiente…
railwaygazette.com/technolog…
what am I seeing 😛
your @AmpCode agents tapping into our very sweated optimizations so they can close the loop fast
playing with a concept for how we work at @tuistdev where signals become channels (e.g. a slow query, unusual error pattern, customer stopped using a feature), looping people in conversations with agents to act on it, and produce an artifact at the end (e.g. email, pr...)
it's very similar to how most companies operate when incidens happen, but applied to how a company can run.
and an agent prioritizes those threads based on the severity of the issue (e.g. it's attributed to an enterprise account)
cargo caching, with collocated cache in our runners, is coming along quite nicely.
the rust support comes with the full package: build & test insights, dynamictime-based test sharding, flakiness detection, and quarantining.
if @rustlang build times have annoyed you, we've got something for you
