2 ms·
If you're genuine about your goal (re-examine your own feelings, it's easy to deceive oneself!), your question is going in the wrong direction. The framework d
by cloogshicer 4y ago
If you're genuine about your goal (re-examine your own feelings, it's easy to deceive oneself!), your question is going in the wrong direction.
The framework doesn't matter.
If you want to release a startup quickly, just do the minimum amount of work to test the hypothesis you have about your user. Most of the time that will not involve programming. It could be as simple as setting up a Gform or calling a few friends and talking to them about their problems.
If it turns out you do need to code, take whatever tool you already know that gets the job done. Crucially, "gets the job done" means: focus only on what you know you already need. Do not plan ahead. Don't think about scalability. You can always re-write if your idea is actually good (which it almost never is).
Do things that don't scale.
However, if you find your motivation is not so much about starting a startup, but more about learning a new framework, just pick the one that's most interesting to you.
- NayamAmarshe 4y ago> The framework doesn't matter. If we're talking about ease of use, doesn't that matter? For example, I could write things in React or use a templating engine or even regular HTML/JS. All 3 options have different ease of use and require certain boilerplate to get things done in the same time. For example, you could use Webflow to create a landing page that would probably take you twice the time if you were to do that in React using regular CSS. You could also use Pocketbase's GUI to quickly setup your DB instead of using Prisma to write relations and migrations and handling all the stuff you wouldn't need to on Pocketbase. So I'm kinda confused about 'framework doesn't matter'. In a sense, it doesn't when I'm talking about using it to build something (I know I can pretty much build anything with them) but when talking about the actual time and work involved, some frameworks might provide some time saving processes others don't.
- cloogshicer 4y agoAt 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 :)
- threatofrain 4y agoInterestingly, this doesn't work on HN (and I'm glad for that). Announcements are off-topic and announcements for things that don't even exist and just want to collect emails tend to get very negative responses. https://news.ycombinator.com/from?site=concise.space https://news.ycombinator.com/from?site=concise.space
- infinity_user 4y agoOne of the best answers IMHO. Should be the top spot. Thanks for your input.