Pedro Piñera Buendia’s Post

Ideas take time to emerge and click to form a story that people connect with. After many years of building Tuist and much thinking lately into what Tuist has been and what it can be, we shaped a vision that we started working towards. We need an Omakase for app development—an integrated experience to empower everyone to build better apps faster. And we are going to build it!

"As part of our work in Tuist, we have to put a lot of thinking into how the Tuist is presented as a product. As developers, we might think that it’s just a matter of solving a problem or a bunch of problems, and putting them under an umbrella name along with documentation and a website. However, when I think of the products that I love and use every day, all of them have something in common: they tell stories." #product #devx #openness https://lnkd.in/dhgz5HUZ

Dagger is amazing. It's exciting to see the creator of Docker continue to innovate on his past work to finally decouple automation from proprietary CI YAML formats and bring some consistency across environments. The right problem is solved at the correct layer. https://dagger.io/

Since Mise, I haven't seen a developer tool that strikes a fantastic balance between simplicity and powerfulness, which we look for at Tuist when deciding on technologies besides betting on standards and open source. But while looking for a tool to generate documentation for an OpenAPI spec, I came across Scalar. I recorded a video with a walkthrough to get a sense of the awesomeness of the tool.

Flakiness detection is our first step in testing, but certainly not the last one. A fast and reliable test suite is critical for happy and productive teams delivering high-quality apps to the store. Hence, having tooling to ensure their tests are healthy is part of our responsibility, too. Amazing job Marek Fořt

Best of all, we have a #nobuild setup. We write raw HTML, CSS, and JS. And yes! It's an interactive app without the absurd complexity common in JavaScript stacks. You can check out the dashboard by yourself: https://lnkd.in/du534Xvr

Openness is often perceived as a business risk, but I look at it differently. When you are open, you are more broadly accountable for your work, and your craft is at stake, so people show the best version of themselves. When you are open, people can build trust through your work and not through third-party auditing companies and certificates. If you had anything to hide, you wouldn’t open it. When you are open, you can invite external people to contribute, which means a diversity of ideas flowing into the project, which leads to better solutions. When you are open, anyone can find the information they need to have the agency to make decisions. The organization is more agile. When you are open, people might end up using your work without paying for it, not worrying about complying with it legally, but those who wouldn’t have paid for the software in the first place become evangelists instead. When you are open, you inspire others to create more open businesses on commodities you might have created. When you are open, you might make some people uncomfortable, but they decide to go a different path. We chose This one for Tuist because we want to build a different type of company—openness for the win. https://lnkd.in/dZzhw7Xe

There’s a piece of value in projects that embrace open source that I noticed it often goes unnoticed. The diversity of ideas that come in the shape of contributions. This diversity is very limited when you run a closed-source company, because your diversity pool is limited by your hires, which often happen in the same country or area where the company is based. At Tuist we’ve shaped an amazing foundation thanks to our wonderful contributors, and they are now stepping into design contributions too. #oss