Alfonso Crawford

If Maddox can run a site like this, so can I

What Problem Are You Solving?

Whenever you're trying to create something, or find something that simply makes no sense as to why it would work the way it does, ask yourself this question: what problem is being solved here?

In your own case, it'll help you stay focused. Your actions will stay on-track as you have a clear objective in your mind's eye of what those actions are for. Decisions will be simpler and easier: what solves the problem stays, and what doesn't solve it goes.

Identifying a problem/solution-combo is basically setting a goal.
Goals are nice; very useful, highly recommended.
Do consider trying it out sometime.

The Fun Question

Self-determination is great and all, but applying that question to the creations of others is where things go from great to entertaining.

  • Why did Twitter ever hire as many people as they did only for the vast majority of them to be laid off with no long-term ill effect on the website? What problems were they solving?
  • Why do some artists thrive one just today launched (a crowdfunding campaign that was fully funded in 4 minutes) while others languish in obscurity? What problems are those two groups solving?
  • How come perfectly good software, that does everything you want, gradually become a slow and bloated monstrosity over time? What problem is solved by this tragic evolution?

At first, these look like unanswerable questions; but, as the Buddha once famously said, "three things cannot be long hidden: the sun, the moon, and the truth." These baffling scenarios actually make complete sense in the context of what they were in response to!

Twitter

Twitter was built on a speculative bubble. Hiring looked like growth, which attracted investors; which spurred more "growth" (hiring), which attracted more investors. People brought money into the company simply by being in the office. Twitter wasn't profitable in the traditional sense, but it was experiencing income. When the website had to start producing income (a new problem), we all saw what happened.

Artists

Successful artists do not merely foist their own inner worlds onto others in an exercise of vanity: they create tools through which others can explore and understand themselves better than they could do on their own. A struggling artist says "look at me." A successful artist says "look at you."

Software

Programmers are hired on some kind of wage or another; hourly, salary, whatever. Employers that have to pay these people on a schedule don't want to hear "there's nothing else to do." Either those code-monkeys find something to do, or they can find someone else to mooch off of! As time goes on, people add things and tweak things if only to appear like their doing something, and thus begins the process lovingly referred to as "enshittification."

Conclusion

Very few things are done for no reason whatsoever. The more nonsensical something appears to be, the more hidden the problem attempting to be addressed. Try not to fall into the trap of thinking some new endeavor is simply stupid and wrong: in fact, the stupider it looks, the more evil it probably is.

Have fun learning that lesson.

Back to You

Doubt is fear, and fear is the mind-killer. What's more, doubt is the vague, whiny knockoff of fear too; but it can still kill you: you just look all the stupider when it happens. Better to not let that happen.

It's easy to get lost in creeping insecurities. Maybe more needs to be done? What if the way you did something isn't the "right" way at all?

Does it solve the problem? Is the problem solved?

In product development, there's something called the "minimum viable product." In a project, the MVP truly is the MVP: it tells you where to go, where you are, and when to stop. Don't be afraid of looking silly, or being mocked by onlookers. If you made a viable product, if you solved the problem, you passed.

Even the rudest opposition can't deny a reality right in front of them. No amount of "buts" after a "yes" can take away from that "yes" if it's in response to "does this work in the context provided?"

And just in case that nagging voice of doubt isn't coming inside of your own head, here's something you can ask instead: "what problem are you solving?"