Hacker News new | ask | show | jobs
by quanticle 5271 days ago
I want to make a small counterpoint. The reason it is so easy for developers to make products for other developers is that well, developers are more motivated to learn and experiment with new products. The old adage, "You can lead a horse to water, but you can't make him drink," applies fully here. A lot of people (maybe even the majority) simply will not invest one second into learning or trying a new thing, even if that learning will immediately translate into greater productivity for them.

EDIT: I should note that there are plenty of non-developers who are into learning new tools and new technologies and there are many developers who are extremely closed-minded regarding the tools they use. Regardless, I've noticed that in my personal experience, someone who develops software for a living tends to be more open to learning and using new technology than someone who doesn't. I don't think that's a controversial point.

For example, I know of people (and not just older people) who insist upon using only one tab in their web browsers. Keeping track of more than one tab is just "too complicated", and they can't be bothered. When confronted by an attitude like that, what can you do? Sometimes, it's just not possible for you to boil down a complicated concept into a simple default option for users. It's something that Apple and Google (with their multi-million dollar design budgets) have trouble with. As an ordinary developer at a small-ish firm, do I really stand a chance?

Another point is that I don't necessarily make software because I want to change people's lives. I make software because I like making software. It's my vocation, and my avocation. I don't always want to spend the time and research necessary to make whatever I've built easy to use. It's okay to have one-off projects. It's okay to build tools for yourself before building tools for others.