I HIGHLY, HIGHLY, HIGHLY recommend you give Steve Huffman's course on "Introduction to Web Development" at Udacity at shot. Unlike virtually every single resource I have found, Steve does a great job of explaining the basics of the infrastructure of how a website works while you are implementing it at the same time. Also, since he does it on Google App Engine, 100% of the "tooling" you will need will simply be installing the app engine runtime. I've found that it is a fantastic introduction to programming for the web. It will give you a solid understanding of the basic infrastructure, and you will then have a good mental model onto which you can slowly graft the many other tools that developers use when making a site.
I felt exactly like you did - and in my case, I had even programmed some in college but found it hopeless when trying to make a "real" product. Today I weave between backend and frontend technologies, preprocessors for my styling, grunt, etc. -- all of the stuff that I was put off by at first. And I'm confident it wouldn't have happened if I hadn't taken that course first.
On the other hand, if you can ignore your tendency to understand things and limit your scope to shallow understanding of the top 1 or 2 tiers of the stack, then you can learn enough to be useful within a short amount of time.
I think that by far the single most important thing is to start the "learning to code" process with a specific project in mind.
At some point in software you will realize that there is more going on than you will ever know in detail and the best you can do is understand the salient points and some things are simply not worth learning.
If you learn java in depth - php will be easy, java script will make more sense. Having learnt one language in depth, picking up most other languages are easier, you'll be in a better position to understand how jquery works.
So what? It doesn't make any difference for a beginner, I'd say it actually helps beginners since it makes programming a easier to approach.
>How about starting with NO language at all.
I hated this kind of advice when I was new, I followed it and my hatred has not subsided at all. Just pick a language and learn this stuff as you go, it will make zero difference and will save you a ton of time.
Different strokes for different folks.
I too learned like you, I first learned Perl by trial and error example and the wonderfully awesome Learning Perl. I learned Java by frustratingly going through it, but once I got it I got it. Learning object oriented Perl and Python feel trivial now, thanks to that experience. Python, btw, feels like it needs to be practiced instead of learned, since I already have the concepts and generalities down.
The question of this thread is, how do we teach beginners the concepts in an interesting way. I realize how much of a genius Larry Wall and Randal Schwartz are when I see threads like this.
Reading books and doing tutorials will certainly help you, but you might get burned out quickly. Working on projects seems like a much better use of your time.
Eventually, you'll have to pick up some books and learn theory, but the main challenge is getting to that point where you'll find the theory useful.
I think the limiting factor especially if one is learning on his or her own, is grit and persistence.
I agree with another poster here - it felt like there was too much to learn just to be able to get started.
I've tried to learn Rails for example, following Michael Hartls' step by step tutorial, and even then I get stuck. Suddenly I'm lost with homebrew, updating my PATH, rvm, gemsets, versions, etc. To build a simple website, I have to learn about nodejs, bower, grunt, API's, databases.
Also, there is just something fundamental about the high-level of programming that I feel is never explained in introduction tutorials. When I've tried to learn Ruby itself, most tutorials start out with the syntax (integers, loops, etc), whereas I'd prefer some explanation around how the code is processed to the result. I know some basic Jquery and I am still confused at how it actually works - how the "instructions" end up at the result in the browser.
I've tried the online courses but I struggle to learn through videos and I just find that these courses never really get you to where you can actually build something. I may just need a mentor or classroom environment.
With all of this said, I've just started a 4 month sabbatical and learning to code is my top priority, so I'll see how it goes...