2 ms·
"Try to solve real problems" is, imo, almost a cop out. It's too vague to be a useful answer to to the question. As for people 'solving real problems'... wel
by mgkimsal 16y ago
"Try to solve real problems" is, imo, almost a cop out. It's too vague to be a useful answer to to the question. As for people 'solving real problems'... well... I've known plenty of people who think they're doing just that. It's often identified as a problem they have themselves, or close friends. They spend time working on it (often too long) without knowing there's already 50 solutions out there.
Which leads to 'research your audience before building'. Well... how do you do that? You need to make sure the people you're asking A) actually have a clue and B) actually give a damn about having a clue.
My other answer, which may be more helpful (but probably not) is
1. I find things that have been problematic for me from a tech standpoint, or
2. I look for interesting tech I'd like to learn more about, and look at industries friends/relatives are in.
With #1, for example, I learned SOLR a few years ago. It's not that hard to set up, but not everyone can due to hosting restrictions. I'd played with the idea of dedicated SOLR hosting, but dilly dallied too long - there's multiple players there now. That's in some ways good - it was not a crazy idea, if they're doing it too.
With #2, for example, I'd like to learn more about Twilio. I'm looking for options to test out Twilio in the context of some current customers by learning more about their business operations. It seems there's a couple places where some custom Twilio integration makes sense, and we'll look to do something early next year. Based on what's done for them, and how that works, there might be a spin-off 'web business' from that.
I hope that helps a bit.