That part was obvious, but the point is that if you're exploring, do it for the purpose of learning and growth, not for tracking metrics.
Thus, hit both sides of a problem and engineer the solution 2 different ways. As an interation exercise it's invaluable, and as a product market fit it's an excellent test of future friction.
Coding isn't building a business, even if it's exceptional. Many of the chefs I've known that are nationally recognized talents fail miserably when they open their first restaurant.
In order to stay humble to your craft, when you're entering into the new one, prioritize the pursuit of learning opportunities.
Good points. I'm really doing it for the purpose of learning and growth (like you said). So far I've learned a lot, and it hasn't even been two full days since my "launch." Now I'm focusing on the ideas. So far, I have a couple. :)
