Working in the open fosters diverse ideas. At Tuist, we're embracing open design and welcoming Asmit Malakannawar to help shape our vision.
Writing
In this post, I explore the idea of a fully open Tuist platform.
This blog post reflects on the importance of living a simple life and the impact of social media on our definition of success.
In a world where companies are increasingly locking us into their ecosystems, it's important to invest in tools and standards that allow us to craft software the way we want.
Automate the continuous release of releasable changes with git-cliff and CI.
This post touches on the models we looked at to draw inspiration to make Tuist financially viable.
With many things competing for our attention, what is truly urgent?
A healthy relationship with technology is possible if we embrace openness.
Fix the not found keychain item issue by making the keychain the system default
Learn about the new PBXObject types introduced in Xcode 16 to support synchronized groups.
In this blog post I share how stories help people connect with the products they use.
In this blog post I reflect on this feeling of falling behind that I've been experiencing lately.
Is JavaScript necessary to enable atomic and reusable components on the web?
While many companies see openness as a business risk, I see it as an opportunity to build a different type of company.
The decision of which technology to use in a project can have a significant impact. In this blog post I talk about the impact that Elixir is having in Tuist.
With Tuist we are running a marathon, not a sprint. It's time to regain patience and perseverance.
As we shape Tuist’s future, we are committed to true open source, embracing standards, and simplifying developers’ lives. It’s not just business
BREAKME.md is a new convention across Tuist repositories to keep track of breaking changes that we would like to introduce in the future.
In this blog post I touch on the subject of parallelism in programming languages and how to achieve it without compromising the ergonomy of the language and the complexity of the programs.
Learning for the sake of learning might not be the most effective way to learn. I'm trying a new approach: lazy-learning.