Agreed, but you have to start somewhere. I think one of the things that turns lots of people off from CS education, and programming in general, is how long it takes to get from just starting out to making something cool.

Of course, of course. All I know how to do is web development (besides some Mathematica for research and dicking-around). This isn't like I am standing on top of an intellectual mountain, shouting down at the ignorant masses gathered below, "Stop worshiping your false golden Rails idols".

If I could add a stage though, it would probably be something like "Cluster 5: Why does my website suck?" Sure it's there, it's up on the WWW, but a website made from someone at Cluster 4 isn't something that is going to make you money.

Cluster 5 is when all the CS comes in. You have to learn about algorithms and data structures and regular expressions and what is actually going on behind the scenes. Yes, you can make a website that does the basic simple "of course, here's an exhaustive search" solution to the given problem. But can you make it fast? Or beautiful? Or, heaven forbid, intuitive? Can you fix it after you try and fail to make it the above three? That's the stage that never ends, the one that doesn't take a week of hunkering down with a textbook to get through.

Cluster 5 is the stage that CS education tries to start everybody at without any prior experience. It works for the imaginative people who can make the leaps about why this matters, but for most it just leaves everyone behind. With web programming, you actually have motivation to learn these weird things about patterns of electrons.

Because, honestly, who wants to make websites that suck?

I agree with this entirely, and I fully understand that web development represents a tiny slice of coding generally and that what I've presented is a tiny fraction of what you need to learn to be a good web developer.

I plan to edit the post a little to reflect what people have said. Hope the title wasn't too misleading.

Dude, yes. Bravo.

There are two things: computer science and programming. you can learn one without being competent at the other.

Programming is programming. I don't care if it is just Javascript on a web page, or if it is C. The key is being able to step through the code and think through exactly what it is telling the computer to do.

When I started teaching my son to program we'd play games like "tell me how to get home from here," and I would pretend to follow his instructions to the letter, showing him how the exacting nature of computer instructions work. Every time he'd use a mistaken preposition we'd pretend we got stuck somewhere, or in the river or something. It was a lot of fun.

Computer science is different. Yes, it's helpful if you are in certain fields, but let's not confuse it with programming.

I think learning to develop websites with languages like python and ruby is a relatively easy way to get into coding. I remember learning to program with c++ and seeing int main()...it just threw me into a world of confusion.

Strongly disagree. That is (and many other examples) are exactly "learning to code". Which is the lowest bar of achievement.

Learning to code is not learning to engineer software / systems.

Agree... the title is misleading. I opened up the page and quickly rushed to close it before any coworkers saw something about web development and assumed I knew anything about it. We only have 1 web interface on our product so its not like its a high risk but it's a lot like AIDS, once you get flagged with web dev it never goes away.

Getting flagged with "web dev" is like getting AIDs. Rofl.