It all started in the 1980s and personal computers. Boys who were nerds and socially inept got personal computers from their parents as something to learn with.

It all started in the 1980s and personal computers. Boys who were nerds and socially inept got personal computers from their parents as something to learn with. Before that it was mostly women who got into programming. http://www.npr.org/sections/money/2014/10/21/357629765/when-women-stopped-coding http://www.npr.org/sections/money/2014/10/21/357629765/when-... The problem is when you are socially inept. Or rather lack social and people skills. You don't tend to be as friendly with other people who ask questions etc. Now not every programmer is socially inept. Just that some programmers have a high level of intelligence at the sacrifice of social and people skills. For example during the BBS era there was a series of computer wars between platforms and debates. In modern times it is war between frameworks and programming languages. No, not every programmer is like that. Programming is stressful at times, and it depends on how well you handle the stress. Sometimes the stress makes programmers angry and snap at people asking them questions because they feel they should have read the manual or documentation or used a help file or something instead of asking them something they could have looked up. Me I was always glad to help others out as a programmer. I didn't have much in social skills and people skills and I was a nerd, but I always tried to answer questions in a friendly manner. I saw other programmers who did not and it did not go well for them so I adapted. I mentored others how to program. Most of the programmers are unfriendly towards new coders because they are competition, and they are not at the level of the programmer yet. It is called biting the noob, and you find it on Internet Forums on programming. Noob being new coder or new person. It is just that they have been a programmer for X amount of years, and some new coder comes along and wants to learn what took them X years to learn. It is a process of trial and error, and learning from your mistakes. At first you will write sloppy code and learn how to write better code later. You find the same thing from people who are experts at Linux and the new Linux user asks them questions, and they tell them to read the manual or man pages.