Pedro Piñera

@pepicrft.bsky.social

@tuist.dev CEO – Software crafter and entrepreneur

Gave Once a home. Once is an automation substrate, like Bazel or Buck, but designed to eliminate the costs of those and be interfaced through coding agents. buildonce.dev If you’d like to optimize anything in your repo. Shoot me a DM and let’s have a chat. #buildsystems

Build once. Reuse everywhere.

Once gives every action explicit inputs, outputs, and environment, so results are content-addressed, cached, and reusable across developers, coding agents, CI, and machines.

buildonce.dev

“It is no longer the hyperscalers. It is everyone, because everyone now wants the loop to close at the speed of inference, and there is nothing more deflating than watching code appear in seconds and then sitting there for minutes to find out whether it holds.” pepicrft.me/blog/the-qui...

The quiet corner

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.

pepicrft.me

“The wave will pass. The products will be quietly deprecated or repositioned. The companies that survive this cycle will be the ones who figured out how to offer compute as a capability that developers tap into, not as a place they move into.” pepicrft.me/blog/sell-co...

Sell compute somehow

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.

pepicrft.me

Find the challenge of designing a company to be operationally efficient sexy, and a good asset to have these days. Just built an internal service for @tuist.dev, Atlas, where we plan to move some of our operations and lean heavily on agents, first starting with CRM tools.

"But the equation underneath has shifted. If there is an agent in the room with you, the layer of convenience you used to rent gets thinner. The case for owning your infrastructure, or at least owning the ability to reason about it, is stronger than it has been." pepicrft.me/blog/the-con...

The convenience tax

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.

pepicrft.me

Can’t avoid but seeing platforms like Railway or Render (and any Heroku-like platform) as unnecessary abstractions as a service in a world of coding agents. We moved @tuist.dev services to k8s and don’t feel we need anything else.

We're bringing Tuist's cache + insights to Gradle 🧱 If your team uses Gradle and slow builds are a pain, I'd love to chat. Looking for early collaborators to shape this with us. Global low-latency cache nodes close to your CI. We handle the infra. contact@tuist.dev or DM me! https://tuist.dev

Tuist now includes links to the PRs in every changelog entry so you can see the code that enabled each feature or fix 🔗 Better transparency and easier to dive into the implementation details when you need them.

A sincere salute to the amazing folks who generously imparted their invaluable insights to us: Shili, Snow, Mohammad Azam, @marcprux.bsky.social , Khoa Pham, Zhong Cheng Li, @joanniso.bsky.social, @pepicrft.bsky.social, @dimillian.app and jaywcjlove

Fatbobman (东坡肘子)@fatbobman.com · 7mo ago

Fatbobman’s Swift Weekly #117 is out! 2026: When AI Fades into the Workflow, Are You Ready? 🌟 The Indie Developer's Trial 📲 Swift vs. Rust 🗺️ Skip 2026 Roadmap 🕹️ How to use Claude Code 💬 Fucking Approachable Swift Concurrency and more... weekly.fatbobman.com/p/fatbobman...