Here is a good link to a project that popped up on HN a while back http://www.bentobox.io , basically pick one of the topics and click toggle what to learn next, and it will show you a sort of progression.
As far as tutorials, just google the technologies name + for beginners or something similar. (there are also links to instructions in the site I posted)
As far as where to go for what it really depends on your end goal and who you're working with.
I.E. for web development, some people swear by Django or Rails or some PHP framework, all depending on their use case and the expertise of the people they're working with.
Figure out what you want to make, research what tool would be best to make it, then learn that tool and the languages/frameworks that compose it.
If you're just looking to make a basic web app, I would recommend using Sinatra (Ruby), Flask (Python), or Express(NodeJS). All provide a very simple configuration to get to the "Hello, world" point, however are extensible enough that you can use them to learn more advanced tools, technologies, etc.
If you want to chat more feel free to shoot me an email at [email protected]
http://www.hn-sentiment.com I wrote this for a hackathon over Christmas. Does sentiment analysis on an entered topic against hacker news posts and comments.
These courses seem like a good way to expand one's experience however I don't think they should be used as a substitute for a formal education. Also with all the free/cheap resources available I don't understand how you can justify spending 8,000 - 20,000 dollars on this. There is no way you can expect to replace a four year degree with an 8-12 week crash course regardless of the length of the days.
I don't see where the hypocrisy is in creating an application that maps the location of tweets with the "F-word" and then not writing the word "fuck" anywhere. It isn't the intention to advocate cursing. The goal of the application for me was to work in a new framework/language set on something that some people may find entertaining. Writing fuck on the about page or not doesn't really change the message, I didn't intentionally do either it just isn't the vernacular I use to write about my development work.
That is correct, it uses both the coordinates and places fields (see more about those here https://dev.twitter.com/docs/platform-objects/tweets ). There were actually substantially less before adding the code to handle "place". Most tweets that are tagged with a place and not specific coordinates use a bounding box which I've handled by just dropping the pin in the middle of the box.
In it's current implementation, where it has no persistent data, I would 100% agree, however if you added a data store for it I'm sure that there are analytics you could implement that might be useful.
I'm actually planning on writing this since the change would be trivial. But that also makes it less appealing to do haha. I will see when I can get it done.