5 ms·
1. Why not jump into something yourself rather than trying to form something with a bunch of random strangers? Honest question. This resembles a lot like a loca
by steventruong 15y ago
1. Why not jump into something yourself rather than trying to form something with a bunch of random strangers? Honest question. This resembles a lot like a local startup weekend (not saying there is such an option wherever you live).
2. MVP in 14 days in some cases is unrealistic without even knowing what it is you're looking to do. Some ideas can be done in a day. Some require several weeks or months to get a few features done for a basic MVP. It all depends on the idea.
- jakecarpenter 15y ago1. Good Question. I (and a lot of others around here, I think) 'jump' head first into projects on our own all the time, and stay totally committed for like the first week. I've got a long list of projects and concepts and a boat load of code that faded into oblivion. I'm hoping that working as a group might keep the momentum going until something is actually produced. Working with a bunch of folks I just met seems like a lot of fun, and they aren't totally random; we at least have HN in common. 2. True, but I think for the sake of this exercise, something should be achievable.
- pace 15y ago2. MVP in 14d is realistic and should be the goal 1. Maybe it's not the perfect way to startup something but at least he's doing something (and not just reading anymore). And who knows, maybe the IRC chat doesn't bring a team but gives him tons of new inspirations and ideas for new ventures.
- donw 15y agoRead the original post again. An MVP Rails app can be built in fourteen days by an experienced dev/designer duo, no problem. But startups aren't just web companies. The idea could be a physical product that requires prototyping, for example, and that's not getting done in two weeks of part-time work.
- deleted 15y ago[deleted]