Pedro Piñera

Really liked this blog post about OpenClaw.

I have to say there was something that felt magic from seeing a bunch of pieces together interfaceable from Telegram, but my usage decreased over time to the point that my only use case for it is something I can already do with Claude and/or ChatGPT:

https://entropytown.com/articles/2026-03-12-openclaw-sandbox/

Made some progress today in my balcony garden. Planted basil, cherry tomatoes, camomile, and mint. Fingers crossed 😊

“A chef who has spent years working with ingredients, who understands the subtleties of heat and timing and texture, who loves the act of cooking itself, will always produce something different from someone following the same instructions for the first time.”

https://pepicrft.me/blog/the-beauty-of-being-open/

We are trying something new at @tuist@fosstodon.org that I haven’t seen anywhere else but thought, why not? We are moving our discussions around our upcoming marketing videos to the marketing forum:

https://community.tuist.dev/t/marketing-video-introducing-mcp/938/1

“It's not that the people building them don't care. I think most founders do care. But the pressure to grow, to compete, to ship what the market expects, can quietly push the product toward a kind of sameness.”
https://pepicrft.me/blog/the-obsession-gap/

I’m looking for feedback to expose a new interface to @tuist@fosstodon.org cache infrastructure

https://community.tuist.dev/t/expanding-tuists-cache-infrastructure-beyond-build-systems/935/3

This year we decided to do some work on our empty balcony and bought some plants for the spring season.

Published a new post on how we think about developer productivity at Tuist.

Three layers: toolchain, compute, and cache.

Toolchain is where the real impact is and the most neglected. Compute is the easy sell. Cache breaks the physical ceiling but only works when colocated with compute and accessible from everywhere.

Without a framework like this, you end up with a product that is a collection of loosely related tools.

https://tuist.dev/blog/2026/03/04/three-layers-of-developer-productivity

We published an RFC for Build Reports in Tuist. The idea is to capture build data across Xcode, Bazel, and Gradle so teams can understand why builds got slower or caches stopped hitting, instead of guessing.

Each build system keeps its own data model so you don't lose toolchain-specific signals that matter for debugging.

We're also exploring MCP tools for progressive build analysis.

https://community.tuist.dev/t/rfc-build-reports-toolchain-agnostic-build-observability-and-comparison/925/1

We started building Tuist from the "roof" - deep in the toolchain, contributing to tools we don't own, investing weeks into problems with no direct financial return.

Most companies won't do this. They'd rather abstract everything away and sell you compute.

But trust is the real currency in developer tooling. You earn it by showing up and doing the work, not by growth-hacking your way in.

https://pepicrft.me/blog/2026/03/02/building-the-house-from-the-roof

https://nesbitt.io/2026/02/26/git-in-postgres.html

We used Codex to migrate Mastodon iOS to @tuist@fosstodon.org Clean builds went from 110.8s to 22.3s (80% faster).

The agent handled the full feedback loop: extracted build settings, mapped targets, fixed errors, debugged runtime crashes. Manual migrations take days. This took hours.

The best output? A reusable skill file so other teams can migrate without starting from scratch.

Try it on your project: https://tuist.dev/blog/2026/02/02/migrating-mastodon-ios-to-tuist-with-codex

Just published our first public case study.

monday.com has been using @tuist@fosstodon.org since 2022. They went from a monolithic Xcode project with constant merge conflicts to 200 modules that any engineer can create confidently. CI dropped from 20+ minutes to 9.

This is exactly why we built Tuist. First of many stories to come.

https://tuist.dev/case-studies/monday

Kicking off the last dev cycle of 2025 at @tuist@fosstodon.org 🎬

Big focus on making cache nodes self-hostable so you can run them close to your CI, office, or even AI coding environments. Latency is going to matter a lot in the Xcode 26 CAS world.

Also working on test flakiness detection and some nice improvements to Previews.

https://community.tuist.dev/t/plans-towards-the-end-of-the-year-in-the-cycle-2025c6/833

With so many improvements and new features landing on @tuist@fosstodon.org, you might want to subscribe to our product newsletter. We send a curated update every 6 weeks, right on your inbox:

https://tuist.dev/newsletter
#Swift #iOSDev