3 ms·
> Just fill needs that you have. Don't like how something existing works? Fix it. Think you can offer a better version of an existing idea? Go for it. While I
by Lyngbakr 2y ago
> Just fill needs that you have. Don't like how something existing works? Fix it. Think you can offer a better version of an existing idea? Go for it.
While I don't disagree with this point, what it often leads to is developers creating developer tools, which is a crowded and competitive area.
There are fields out there that are crying out for tech solutions because they are lumbering dinosaurs that haven't changed with the times. One example is the maritime industry. It's amazing how much is still done with pen and paper on a ship. True, there is often a reluctance to adopt new tech, but the younger cohort of mariners are far more eager and receptive to tech solutions than the previous generation.
My suggestion is to look for those industries and talk to folks in those fields about their pain points. The bar may be so low that you could step over it.
- rglover 2y ago> While I don't disagree with this point, what it often leads to is developers creating developer tools, which is a crowded and competitive area. That can certainly happen. But you should at least have some domain experience or have a partner who does. Otherwise, not only will it be hard to come to the correct solution, you'll struggle to get your foot in the door to the industry.
- Lyngbakr 2y agoAgreed: you don't want to create a solution to a hypothesized problem that doesn't actually exist. My point is that there are low hanging fruit if you step outside your immediate bubble, but — as you say — you'll need a guide.