How to Decide What to Build
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 startup ideas. To the point where I'm just consulting at the moment because I can't think of any startup idea to work on.I mean I have ideas of problems I want to solve - but they've all been met by massive resistance because they're huge problems. Like for instance one idea I had was I hate making food, but I don't want to eat out all of the time. Can you crowdsource cooking from your neighbors? So I tried building that platform. I instantly discovered there were huge safety regulations about cooking, and that really baking (or anything that isn't extremely perishable) is the only thing you can pretty much do out of your home and not get slapped by the state for violating health codes. So I'm just sort of defeated...the only problems I want to tackle just seem massive and I can't seem to find the divide-and-conquer algorithm to help the world in a smaller (but still meaningful) way.