Live data from Hacker News

How to Decide What to Build

dcgross.com

1–10 of 179 posts

Re: How to Decide What to Build

#2
> Focus on the repeat offenders. The ideas that you keep coming back to.

I totally buy this. Linked to it, I think the it's good to be able to entertain obviously bad ideas for a short while. You think of an idea because of some set of underlying prompts, so even if the idea as a whole doesn't have legs, there are often insights lurking somewhere in it that you'll end up coming back to.

Re: How to Decide What to Build

#3
I like the advice to actively record your ideas (every little one). Thinking about things in abstract, it can seem like all the good problems are solved, but listed out on paper it is a lot easier to analyze and notice patterns.

Re: How to Decide What to Build

#5
I like the idea of just decide on something to build and than build it. Worst case scenario you get a learning experience. And I like building things I enjoy or products I really wish I had. So I get benefit in that way. With software inputs outside of labor are low, so you won't lose out financially in most cases.

Re: How to Decide What to Build

#6
post #4

“everything in the world was created by people no smarter than you”. Is there actually any validity to that? Assuming you is a human of average intelligence...

It’s certainly false though the sentiment might still be valid, basically that the lack of smarts isn’t something that’s holding up more inventions from coming into this world.

Re: How to Decide What to Build

#7
Customers are also a great source of project ideas. You can pick a customer, like "small business owner" or "wealth advisor," and interview them.

My favorite question that leads to ideas is "tell me everything you did from when you started your day until now," and dig into all the annoying/painful things they mention.

Re: How to Decide What to Build

#9
post #4

“everything in the world was created by people no smarter than you”. Is there actually any validity to that? Assuming you is a human of average intelligence...

I think what he meant is that if you look into the process of how products and system are designed, you will likely find out most of them quite comprehensible, and more than often made by a group of men/women that are not necessarily passionate about it. Hence with great passion and even average intelligence, there is no reason we can not achieve a far better product than the current one.

Re: How to Decide What to Build

#10

I like the idea of just decide on something to build and than build it. Worst case scenario you get a learning experience. And I like building things I enjoy or products I really wish I had. So I get benefit in that way. With software inputs outside of labor are low, so you won't lose out financially in most cases.

That is FAR from the worst case scenario.
Post reply on HN