4 ms·
At the beginning (which from your post I assumed that's where you are, sorry if I misunderstood), it doesn't matter since you will (should!) have very few featu
by cloogshicer 4y ago
At the beginning (which from your post I assumed that's where you are, sorry if I misunderstood), it doesn't matter since you will (should!) have very few features. Those will be fast to build in almost anything.
Code is a liability. The more code you have, the more you have to maintain, improve, etc.
Now, if you already have a customer base, it's a different story - but then your idea has already been validated.
My main point is, don't obsess over these decisions until then. It's very easy to fall into this trap (I have several times), where you deceive yourself that you're building an MVP, but really you're building this huge complicated thing that nobody really needs.
Michael Seibel (YC CEO) has a great video where he talks about many people (myself included) kinda want to be artists, so they make something that is like art, when really what you need to build is something to be thrown away. https://youtu.be/1hHMwLxN6EM https://youtu.be/1hHMwLxN6EM
- NayamAmarshe 4y agoThank you for the advice!
- cloogshicer 4y agoYou're welcome! I just realized I linked the wrong video, here's the correct one (also Michael Seibel), where he talks about art: https://youtu.be/C27RVio2rOs?t=1119 https://youtu.be/C27RVio2rOs?t=1119
- NayamAmarshe 4y agoThe wrong video was very helpful as well to be honest, so thank you for it :) Helped me realize I was thinking about my project in the wrong way. Hopefully will release in the next few weeks :)