[ekianjo]

Good point, but I think that is why there are more and more people preaching for teaching Everyone to learn coding. Education and support on how to help those users help themselves is how you can help. Anyway, there are far too few programmers to solve all the world's problems, so increasing the number of people being able to program something is a step in the right direction.

[route66]

You just describe the complete and utter failure of Nerdistan: While the nerds solve their problems by writing software that caters for their nerd-needs (version control, editors, fluffy frameworks just yo name a few) , the rest of the world should just learn to program themselves when they want to solve their problems ...

There is a way out of this echo chamber though: don't teach others to program but let them teach you about their field.

A software industry who only caters for itself (the "scratch your own itch" fallacy) is irrelevant. How many Basecamps do you need?

[ekianjo]

I know what you mean by "let them teach you about their field", but I think the point of the whole discussion above was that you cannot design a very good product unless you use it yourself. I dont remember who said that in the first place, but I remember such things as "men can't really design stuff for women, because they don't really understand how they think". I am not sure if it applies to everything but there is some truth in that. In software, you can see a similar trend: Facebook is a good social tool because the funder actively uses it all the time. The iPhone is a decent phone because the CEO was going to be an active user. I have heard tons of stories from friends/coworkers where design decisions are taken by non-users, and they usually fail miserably once on the market.

I agree with you that spending a lot of time with others who are not like you is definitely an improvement, but it is still not going to be as good as if they were able to do something on their own.