4 ms·
I wonder why that is – is it because I’m more eager to hack on early prototypes of fun ideas than continue them? Or is it because the code base is so developmen
by michael_dorfman 16y ago
I wonder why that is – is it because I’m more eager to hack on early prototypes of fun ideas than continue them? Or is it because the code base is so development-unfriendly that working on it is just no fun? (For example, there’s no automated testing.) Soliciting feedback.
It seems to me that you might do well to try to find a co-founder to work with. You're clearly full of ideas, and have the skill and discipline to get an MVP out there. Nicely done.
However, I think that having somebody to share the ideas with, prod and poke you, and share some of the burden, might help you achieve more.
- swombat 16y agoI'd disagree with that. Getting a cofounder before finding an idea that sticks will: 1) slow you down - you can't iterate as quickly when you need to convince someone else too 2) dilute your shares a lot more than if you de-risk the idea before getting others involved Given his choice of a "quick iteration" approach, I don't think getting a cofounder makes sense.
- deleted 16y ago[deleted]
- imp 16y agoHe seems to be doing okay with building initial products and then selling them off if they have potential but don't interest him anymore. I would guess that adding a co-founder would put more pressure on him to stay with a project that he wasn't committed to. At least he's honest and aware of his dedication to each project.