Ask HN: How do you decide which “great opportunity from a friend” to work on?
I am in a rut in my day job and so I would like to work on both if I can because they would help increase my skillset. Both are greenfield projects so I can choose any code set to work with which means I can shore up skills that I don't have or have let languish. But I am not sure which project to go with.
One is a problem that is explained by the business as something that if solved would help on boarding of customers and be able to be cross sold to other business of the same type.
The other is a project that while the primary has thought it all out the target audience is aimed primarily at users who are not computer savvy.
I can provide more details, but I am curious what constraints or measuring sticks HN uses when pursuing a project that doesn't have an upside any time soon.
2 comments
[ 3.3 ms ] story [ 12.2 ms ] threadIf they will not willing to pony up $$ to solve the problem it isn’t worth doing. It doesn’t have to be your friends that pay but potential/first customers. If you think you/they can’t sell something that doesn’t exist either your sales people are not as good as you think or the idea does not resonate or solve a painful enough problem.
If you build it they will come is b.s. If you sell it now you will sell a sh*t ton later is a much better moto.
Most times I never hear about it again, and thats the goal. If they can't be bothered to write a simple email about their idea, it's not worth anyone else's attention.