Problem-oriented solutions

[pepicrft]

Hi there!
Over the years being part of designing and building tools for developers, I've noticed that we developers tend to incline ourselves towards solutions and forget about the problem. I think it's natural because we get very excited by building things, but it has an important caveat that I'd like Tuist contributors to be very aware of: we forget what we are solving.

I believe, the reason why many tools these days are complex is that they are designed disregarding the problem. I add this flag to customize this directory, this other one to be able to customize this other thing, that one to opt into this thing which I think is cool. No! Users come to us because they have a problem or a need. They don't tell us they need a new command or a new argument. They tell us what we need, and we contributors, have to make sure we design and build the simplest solution that helps them.

As a contributor, you'll often find yourself in the position of turning a problem into a solution. You'll feel tempted to add flags everywhere, new commands, a lot of flexibility. You'll probably think too far ahead about ways people will use the feature. Please, don't do that. We need Tuist to remain simple. We need Tuist to solve problems and not expose developers to tons of options that overwhelm them. We exist because that's what Xcode is doing, and we don't want to fall into the same trap.

Let's solve one thing at a time. Let's make sure we add features as needed. Let's make sure we optimize for simplicity. Let's make sure we understand where people are coming from when they open issues saying I need X. Let's continue to make Tuist that awesome tool that people love because we've managed to keep it simple, well organized, and problem-focused.