Live data from Hacker News

How to Decide What to Build

dcgross.com

41–50 of 179 posts

Re: How to Decide What to Build

#41
post #34
post #29

I've always had lots of ideas, just none I've wanted to follow through on, now I'm in the early stages of an idea I think will be useful ( at least it will be for me ). It's an idea that was simplified out of another idea that's just too large for me to tackle at the moment. In fact it's an idea that's been part of a variety of other ideas. It's also part of a number of other peoples products, and is probably one of…

Use C#.

I am using C# on both .net core and framework for the bulk of it.

Re: How to Decide What to Build

#42

Earlier quoted context omitted.

Yep, you're definitely not alone here. I also find that sometimes I can think of problems that aren't really a single problem but a whole category of problems, and I have no idea which particular piece I'd like to break off, or any idea for a solution.

Exactly. Because breaking the law really shows your integrity. Especially regarding food intake, where one un-hygienic perdon could endanger the lives of many. Personally I like the idea of regulation to ensure a minimum level of quality and security. Look at the aviation industry. Just as an example. What do you think makes flying one of the safest methods of travel? It is easy to dismiss regulations as hindering. B…

Hey, I think you meant to respond to tropshop, not ajdlinux :)

Re: How to Decide What to Build

#43

One of the points the author makes is that you should track the problems you have, and the ones that reoccur will be good signals to solve them. Does anyone else feel pretty content with what they have? Because this strategy I think Paul Graham has talked about in one of his essays for ideas. And to be honest, I do genuinely feel like I don't have much if anything to complain about, and so I can't really think of sta…

I can relate to your sentiment of being content with what you have. I gave up my smartphone, I canceled all paid subscription services, I use linux and open source software for everything.

Basically, it's difficult for me to imagine personally paying for any type of SAAS offering, so when I'm working on a project with a paid model, sometimes I have to employ a 'suspension of disbelief' because I'm working on something that I know I probably wouldn't be willing to pay for (not because it sucks, just because I'm hesitant to pay for any software or online service).

Re: How to Decide What to Build

#44

One of the points the author makes is that you should track the problems you have, and the ones that reoccur will be good signals to solve them. Does anyone else feel pretty content with what they have? Because this strategy I think Paul Graham has talked about in one of his essays for ideas. And to be honest, I do genuinely feel like I don't have much if anything to complain about, and so I can't really think of sta…

I don't normally talk about this, but here is what you are missing: Businesses that make (real) money revolve around one of two ideas: - They sell shovels - They are middlemen (middlepeople?) They sell shovels. This is stolen from the old saying that during the American gold rush the people who made the money were the ones selling shovels. Or facilitating others to go and do what they wanted (in this case, chase a wi…

Thank you for this thorough and thoughtful response! Lots to soak in here. I agree, I am certainly not Elon Musk, there is no ego here. I'm just saying that the problem spaces I want to help with (environment, health/fitness/healthcare) don't seem like the problems I can effectively tackle because, as I mentioned before, I can't seem to find a way to divide-and-conquer into a smaller idea I can execute on. Do you have any thoughts behind that? I guess maybe talk with people in those spaces and see what problems they are having that could benefit from some tiny innovation?

Re: How to Decide What to Build

#45

One of the points the author makes is that you should track the problems you have, and the ones that reoccur will be good signals to solve them. Does anyone else feel pretty content with what they have? Because this strategy I think Paul Graham has talked about in one of his essays for ideas. And to be honest, I do genuinely feel like I don't have much if anything to complain about, and so I can't really think of sta…

Ideas are a dime a dozen, execution is what wins (or sometimes you just get lucky).

Your cooking annoyance is a good place to do thought experiments. I don't always want to cook, but in cases where I don't want to cook I don't always want to go out. Proposed solution: Get my neighbours to cook for me. It's a good idea, but after you investigated, it was infeasible.

There are two ways you can go with this. First, you now have a new annoyance: normal people can't sell their own food creations without poisoning people (or, alternatively, the government discourages people poisoning each other :-) ). Nothing is saying that you have to stay with your original annoyance. You can move. And since this is a thought experiment, maybe you might come up with another idea and investigate that. If it doesn't pan out, then you will get new annoyances.

This technique is pretty similar to Toyota's "5 whys". Before they decide on how to fix a problem they first ask why the problem exists. When they answer that question, they ask why that situation exists. They go down 5 times (I don't think that number is actually carved out in stone, but you get the idea). At that point they have a much better idea of the situation and can choose the most effective place to solve their problem.

But you may come to a realisation that "getting my neighbours to cook for me" is not going to be feasible -- and that nothing down that chain is going to work out. That's not a problem, because it's not the only solution to the problem.

For example (and feel free to steal this idea) I live in Japan and my wife was ill the other day. Normally she makes me a packed lunch. I was too busy with work to return the favour, so instead I went to the convenience store and bought some instant ramen.

You may have eaten instant ramen before. When I lived in Canada, I learned how horrible it is. But in Japan, if you spend $2 instead of $1 the instant ramen is pretty freaking good. If you spend $3 instead of $2, it's almost as good as I can make myself (the only real downside is that the toppings are not really numerous enough).

I thought to myself, "I wonder if I could export these amazing ramen soups to the US. I'm sure you can get them in specialty stores, but this is absolutely ripe for exploitation on the web. These things weigh nothing and they will ship perfectly. And they don't rot in any reasonable time frame. Why the heck is there not anything like this?"

So I did my 5 why's and realised that if you want to do it, you have to be in the US (or wherever you want to sell) because you need to order container sized amounts to make the overseas shipping reasonable. This means you need a distribution centre at the destination. But I absolutely guarantee that Nissin (or whoever you want to talk to) would be thrilled to sell you a container of ramen, with which you can do a "Ramen of the week club" on the internet (surely this already exists... surely... I haven't actually checked).

Anyway, that's an example. Don't give up is the answer. One idea is nothing. Let it go. Use it to inform your next move. Keep going and never stop.

Edit: I just had a quick look. There are internet ramen clubs, but their ramen is all crap. Ripe for disruption -- look for ramen in a bowl shaped container.

Edit Edit: Darn: https://japanramenbox.com This is exactly what I was thinking. Hope they do well (though you might be able to undercut them ;-) ).

Re: How to Decide What to Build

#46
post #38

One of the points the author makes is that you should track the problems you have, and the ones that reoccur will be good signals to solve them. Does anyone else feel pretty content with what they have? Because this strategy I think Paul Graham has talked about in one of his essays for ideas. And to be honest, I do genuinely feel like I don't have much if anything to complain about, and so I can't really think of sta…

This only applies to US and a bunch of other countries that would bother to enforce the law regarding cooking regulation. Most countries wouldn't really care as they have more important issues to solve than clamp down on innocent people making informed choices about their lives. So the idea isn't really bad.

> Most countries wouldn't really care as they have more important issues to solve than clamp down on innocent people making informed choices about their lives. So the idea isn't really bad.

Yup. More important issues like no rule of law, no sanitation, low literacy rates, mob rule, etc.

"Clamping down on innocent people making informed choices about their lives" is what you get to once you stabilize a society and solve its most urgent, life-threatening problems. It's what you get to once people are living in relative health and safety, and then you discover that "informed choices" aren't really that informed, because they're made in the environment full of scammers and people who can't give two fucks about other human beings, if it means few dollars more.

And once you get to that, you can live in a world where food poisoning in a restaurant is national news.

Re: How to Decide What to Build

#47

One of the points the author makes is that you should track the problems you have, and the ones that reoccur will be good signals to solve them. Does anyone else feel pretty content with what they have? Because this strategy I think Paul Graham has talked about in one of his essays for ideas. And to be honest, I do genuinely feel like I don't have much if anything to complain about, and so I can't really think of sta…

I feel like people - us, here, on this forum - sometimes think too big. Like, we have to invent the new Facebook or it’s not worth it. I think that can cripple our thinking.

(Obviously I’m massively generalising. I’m not having a dig at anyone here.)

I’ve realised recently that there’s good money to be made solving little problems. Not Zuckerberg money, but who wants that lifestyle. Ramen money.

Example: my partner is a medical copywriter. Some jobs, she spends hours reformatting journal citations. All she’s doing is making part of it italic, making sure the dashes are all en-dashes, whatever.

How many medical copywriters are there? How many people have this problem? Now, it’s not a life-changing thing, but it’s what computers are for! So we’re building a little tool that will make this easier for us.

What’s our goal? I don’t know. To make enough to pay our rent? That’d be lovely for starters and what is that, a thousand people giving us $5/month each? That’s nothing.

It also helps, of course, that she’s in this industry. She knows where to go to find other people with the same problem. Solve something in your domain, and everything’s going to be easier. (It’s also why I’m not afraid of telling everyone here what the idea is. Chances of someone else being passionate and knowledgeable about this, enough to steal the idea, are near nil.)

That’s where my head’s at, and it makes thinking about this stuff much easier for me, at least.

Re: How to Decide What to Build

#48

One of the points the author makes is that you should track the problems you have, and the ones that reoccur will be good signals to solve them. Does anyone else feel pretty content with what they have? Because this strategy I think Paul Graham has talked about in one of his essays for ideas. And to be honest, I do genuinely feel like I don't have much if anything to complain about, and so I can't really think of sta…

Did the massive regulation on the taxi industry stop Uber? If you build something people find genuinely useful, you will become a force that causes the market to adapt. Regulation follows innovation.

I'm founding Uber for Biotech. No biosafety regulation is going to stop us from CRISPRing our way into better future!

Seriously though, I get that archaic rules need to be fought in order to be changed. But there are proper ways to do that, and Uber did it in about the most antisocial way possible aside from murdering people. Please, don't be like Uber. Innovations need a stable society to flourish.

Re: How to Decide What to Build

#49

One of the points the author makes is that you should track the problems you have, and the ones that reoccur will be good signals to solve them. Does anyone else feel pretty content with what they have? Because this strategy I think Paul Graham has talked about in one of his essays for ideas. And to be honest, I do genuinely feel like I don't have much if anything to complain about, and so I can't really think of sta…

Having a pain point and validating it with a set of other users is a good vector for success. While that is true I have seen/heard/read many ideas that are brainstormed in a room and selected at random becoming widely successful.

Anyway, regarding food you could have thought about a machine/robot based solution, at least to begin with :)

Re: How to Decide What to Build

#50

One of the points the author makes is that you should track the problems you have, and the ones that reoccur will be good signals to solve them. Does anyone else feel pretty content with what they have? Because this strategy I think Paul Graham has talked about in one of his essays for ideas. And to be honest, I do genuinely feel like I don't have much if anything to complain about, and so I can't really think of sta…

I mean... you may not be able to distribute food, but as far as I know, it's certainly not illegal to create a social networking app where someone can say "I'm interested in a sandwich" and another person says "I'll make you a sandwich for $5". If Tinder is legal, I don't see how that could not be.
Post reply on HN