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.
Writing
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.
I redesigned my website to make it visually simpler and added new pages.
In this blog post I talk about a recent emotional breakdown that I had and how I'm processing it.
In this blog post, I explain why you might need to set the -ObjC flag in the OTHER_LDFLAGS build setting of your Xcode project.
In this blog post I share the principles that we embrace at Tuist to build a future-proof productivity platform for app developers.
In this blog post I reflect on why I believe not more organizations are adopting Bazel and why Tuist is taking a different approach.
Open-source sustainability is hard, and while it’s necessary to have the tools to reward and pay contributors for their work, the problem requires more of us, developers, speaking out loud about the importance of contributing to the software that we depend on.
A reflection on the importance of maintaining the open-source projects that become the infrastructure for many companies.
In this blog post I share how we used Cloudflare Workers to connect AppSignal with Incident.io.
Proprietary solutions are a dime a dozen, but standards will outlast them all.
In this post, I share my thoughts on open source and how it aligns with my principles. I also talk about the different models that I've seen in the industry and how I'd like to see it evolve.
Ruby proved not to be the most suitable runtime for apps that are IO-heavy. We evaluated Swift, but ultimately decided on Elixir for various reasons.
In this blog post, I talk about the scaling challenges we faced with Rails, and why we decided to transition to Elixir.
In this post, I reflect on how the digital world has hijacked my attention and what I'm doing to gain it back.
Schemes in Xcode have an option to run tests in parallel, but if your code isn't designed for it, you are in for a world of pain.