Ask HN: Honestly, why are there so many "how to learn to program" asks?

[maxbrown]

I'm genuinely curious why there are consistently at least 3-4 new questions about how to start programming or what language to start with, etc. etc.

Do you think the askers are following through, and actually learning based off of the recommendations? Is it a band-wagon sort of thing? Is there any way to compile the information in one place and point askers towards that?

[dwc]

This isn't a new problem.

    Do you think the askers are following through, and
    actually learning based off of the recommendations?

Some do, but most do not.

    Is there any way to compile the information in one
    place and point askers towards that?

This has been done so many times over so many years that there's a plethora of pages out there (http://www.google.com/search?q=learn+how+to+program), some current and others in various stages of decomposition.

A truly motivated individual is likely to realize that this question is Googleable and will find tons of information. That leaves us with the occasional capable and motivated person asking for some guidance that HN could uniquely provide, and the rest of such questions are less worthy, IMO.

Making a nice resource, perhaps with some HN flavored info, would be really great were it to be referenced. The best case to me would be that "how to learn programming" posts would get no up votes and a single comment linking the resource. Or something along those lines.

[maxbrown]

I'm sure it's not new, it just seems to me to be flaring up recently.

A truly motivated individual is likely to realize that this question is Googleable and will find tons of information.

Agreed. And there are many other HN-related routes too - I've had great responses asking questions of HNOfficeHours individuals.

Making a nice resource, perhaps with some HN flavored info, would be really great were it to be referenced.

Do you think a compilation would be referenced enough to make it worthwhile? Sounds like a valuable side project if it would actually be used.

[JoeCortopassi]

I think that the main reason that this question comes up so often (only to have it's answers essentially ignored) is because, "How do I learn how to program?" isn't what they really want to know. Programming, in and of itself doesn't take much to learn. A person with average intelligence can learn the syntax and basic idea of a language in a day.

I believe the question they really want an answer to is, "How do programs work?".

If you really boil down the initial appeal of programming, it isn't Python/C/PHP/Ruby, it's learning how to make the things that those languages are associated with. People are fascinated by programs that can sync files between computers (dropbox/Python), share pictures on the internet (facebook/PHP), or cause your computer to run (Linux/C).

I think the best way to help somebody with this question is to find out what it is about software that fascinates them, then suggest a language/framework that facilitates that.

[brudgers]

There are so many "How do I learn to program?" questions because:

1. Asking the question on HN is a hell of a lot less painful than actually sitting down to learn to program.

2. Reading the answers feels a hell of a lot more like progress than eight lines of code that still doesn't work after four hours.

3. Programmers are more willing to answer "How do I learn to program?" questions than cellists are willing to answer "How do I learn to play the cello?" questions.

[tnorthcutt]

I think you see this for the same reason you see people endlessly debating/discussing version control systems, GTD, IDEs, OSes, keyboards, mice, browsers, etc. etc. etc. They're all just tools, and yet we (myself included) spend far too much time talking about them, and not nearly enough time using them. True, some of the discussion is merited and is rooted in useful thought about real differences between tools, but much of it is over analyzing.

I think much of this could actually be rooted in fear, which drives procrastination in lots of people - more than most of us realize, I think. Merlin Mann's gave a great talk on fear: http://www.youtube.com/watch?v=Lk0hSeQ5s_k

The key is to understand that fear isn't going to go away completely, and to still keep doing, even though you're scared.

Enough talk. I'm going to go build something now.

[rdin]

I think part of it is that everybody has their own opinion of where others should start. For example, some people think that new programmers should start low-level (such as with C) and learn how memory management works; others think that a higher-level language (such as Java) is better and abstracts away all of the things that people can learn later. And of course, there's also web app programming, which brings in another curve

[maxbrown]

So maybe a resource of compiled answers could offer a flow-chart of differing opinions?

IE if you want to learn this, start here. If you think this is more important, start here.

[lovskogen]

Myself, I want to learn basic programming to build stuff. Being just a designer, limited to front end – is limiting. I would think the same goes for some programmers, wanting to learn user experience and interface design. I think we'll see more people knowing how to build things, code and design. Like Shaun Inman.

[bendmorris]

My question is, why are so many people upvoting these threads? People should be encouraged to use Google as their first resource before posting questions on Hacker News. Even if you haven't been here long, you could probably guess that such a basic question has likely been asked before.

[jrsmith1279]

I'm betting a lot of them are people who have an idea and want to build it instead of either hiring someone or trying to find a tech co-founder.

[triviatise]

It's a good way to get a lot of karma? People don't think to do a google search?

[themonk]

Person asking such question wants to validate he learned it right way or not.

[jcr]

Personally, I believe they're trolling.

[mariusz10jonski]

I left one just a second ago