As soon as you are able to write a basic program in JS then jump right to AngularJS.
Tkae a look at this book as well. http://shop.oreilly.com/product/9780596805531.do
It's really helpful.
Your third paragraph is completely sensible however. The Good Parts is horrible if you're a beginner programmer, and I'd definitely recommend against it. But if you have a CS degree or years of programming experience, it should not cause you trouble - it's a great, terse intro to JS that'll get you up and running in no time.
In addition to LPTHW and dbond's very complete suggestions:
$ sudo apt-get install python-doc
This is not installed by default. It will install the entire python.org documentation site, probably at /usr/share/doc/python/html/index.html
Decide whether you want to use python2 or python3. Python 2.7 is probably what's installed by default on your linux distro (unless you use Arch). The following is not in the installed docs, it's an external site:
Read PEP 8
$ aptitude search python |grep framework
$ sudo apt-get install sqlite3
Install a database. sqlite is lightweight and more than good enough for learning, and won't bog you down with learning how to run a database server. Alligators and swamps ...
I wouldn't bother installing a web server, python comes with a rudimentary web server module.
General background on python web programming: (skim it)
The module you'll likely use to play around:
Learn the python debugger, it's rudimentary but very helpful when you're learning.
Learn the python REPL, or the interpreter as they call it in the docs.
Install, learn and use a better python REPL:
sudo apt-get install ipython
If you can afford it, Oreilly has some good ebooks.
If you can't afford it, but you can afford the weight, search for books you like on AbeBooks: (used or internation edition books)
Dive Into Python is available online and downloadable: http://www.diveintopython.net/
Eventually you'll want to know more about sql: http://news.ycombinator.com/item?id=5087439
Learn you a shell:
Install vim and emacs and decide which one you like, but any simple arrow-key-based editor that comes with your desktop is good enough to get started.
Install git, eventually you'll lose some work and you'll see the light. Just go real basic with git if you haven't done much source control before. Don't get bogged down in learning git, you want to learn python and web programming. As you go, you'll eventually want to know more; you'll know when that is.
$ sudo apt-get install git
Appropriate first web projects would be any of the example projects that come with the lightweight framework docs.
Appropriate first python-specific projects would be the same, in whatever python tutorials you like.
Appropriate next projects would be whatever catches your interest as you're going through all of the above. Keep a notebook/file of project ideas. Actually that would be a nice first project right there, a simple web app for a project notebook.
EDIT: Also, learn to rely on the man pages.
$ man man
$ man bash
$ man python
$ man -k python
$ man woman
No manual entry for woman
The other advice I'd give is that, while I wouldn't go too far to play down the importance of learning to code through formal education, I think you can completely teach yourself since you have the passion for it. I'd say do a combination of the two as it fits you. Because at the end of the day, the most valuable thing you can have on your resume is that you've built some cool stuff. And if you're excited about learning to code, you'll find yourself building cool stuff in no time. Well - okay, "no time" really means a lot of hours of reading and coding, but you'll get addicted really fast so it'll feel like no time :) Anyway, good luck!
1) It's self contained. No dependencies on third party OO libraries or frameworks.
2) The code is very readable.
3) It's a canvas library, so it's fun to work with if you're into graphics and visualizations.
4) You'll learn a lot about how many JS projects are built, documented, and tested, if you get it to build and the tests running on node.js.
Here is what I would do:
1) Check out the project and get it building.
2) Read all the files in the util folder. You'll see a lot of methods added to Object and Array.
4) Then take a look at the base class: https://github.com/kangax/fabric.js/blob/master/src/object.c... and an inherited class: https://github.com/kangax/fabric.js/blob/master/src/line.cla...
5) Search for instances of the "bind" method, and see how they're used.
Finally, this is just a personal opinion, but I don't like Crokford's chapter on OO JS. I just don't think it presents your options well. If you decide to write a large project in JS using OO techniques, I think you'd be better off utilizing an OO library, compiler, or framework like TypeScript, Google Closure, Prototype or CoffeeScript, than you would charging forward armed with Crokford's chapter on OO.
At the moment, blog posts and online tutorials seem to be the way to go, though you have to be careful there too. Node seems to be moving very, very fast, so things will likely require a medium amount of tinkering, even if they were written two weeks ago.
Personally, I'd pare that schedule right down. If you don't need a specific language, I'd start by learning the basics with Python. It's clear, readable, comes with a brilliant standard library, is very useful for all sorts of things and is a fairly 'normal' high-level language - what you learn in Python will be very broadly applicable.
You'll pick up HTML and SQL by default and while it's worth having a book or two on standby, you'll probably find yourself learning what you need as you need it.
As regards books:
Now go out and build something.
Here are some books that I have used that have been helpful
PHP and MYSQL for Dynamic Websites
I'm waiting for the 6th edition:
You must understand that you need to learn 2 separate things and you need to learn them well.
Learn what's in this book! Go through all the exercises and tutorials. Build something. You can augment the book with tutorials you find on-line (ex. Webmonkey). Then you can View Source on any web page and understand what they did (and what they did wrong).
Only after you have a solid understanding of the basics of these 2 technologies should you consider a framework. This can be tricky. If you adopt a framework too soon, you may run into a problem for which you don't understand enough about what's going on under the hood because you never learned it. If you adopt a framework too late, you'll be hand coding everything and will never get done.
Most importantly: you can only learn any of this by doing. Time consuming doing. Books and resources any necessary but hardly sufficient.
Do not fall into the trap of only learning at the surface and expecting to find someone else to do the coding. This does not work for a small software start-up. You must dig deep and learn well.
Thanks for finally posting. I hope you came to the right place. Get to work and keep us posted.
Get dozens of book recommendations delivered straight to your inbox every Thursday.