5 ms·
Love it. Here are some thoughts. I think you should A/B test the entire project. How you do that is up to you, but I'm sure the community could have some fun
by nickler 14y ago
Love it. Here are some thoughts.
I think you should A/B test the entire project.
How you do that is up to you, but I'm sure the community could have some fun with it.
If you create an app for the consumer side, create another one for the vendor side, and see how the problems conflict, or explore the synergies.
If you build something that searches, build something that turns those searches into social discovery or sharing.
If you build something that floats, build something else that seeks to sink it. Chaos monkey comes to mind.
I recognize it isn't true split testing, but you might discover a part of a chain that others have been ignoring, and you might also ignite a passion for a problem you didn't realize you had.
Best of luck.
- orangethirty 14y agoThank you. Yes, I do plan on testing everything. In fact, this post was a test.
- nickler 14y agoThat 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.
- orangethirty 14y agoGood 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. :)