>you don't know what exactly is the benefit and outcome of all this learning and how it fits in web development This is not your fault; most tutorials and intr

>you don't know what exactly is the benefit and outcome of all this learning and how it fits in web development This is not your fault; most tutorials and intros are horrifically coded and introduced. You'll often find obscenely arbitrary examples that have literally no place in actual coding. Take for example Backbone.js' introductions. It's an incredibly powerful tool for front end MVC work, but it took me a long time to "get it", because there are literally no examples on their site that pertain to any realistic or practical usage of the framework. To wit: http://documentcloud.github.com/backbone/#Model http://documentcloud.github.com/backbone/#Model They themselves admit that this is a useless example, but choose to use it anyway. It confuses the Model and View purposes, and if it appeared in any actual implementation of Backbone, would break just about every convention in existence. Why even use it? I know they want to avoid telling people how to use it, because it's so open-ended, but it doesn't hurt to establish some common practices or mechanisms. It took me a long time to figure out a good way to link models and views agnostically, simply because they don't address that whatsoever in the docs.