Assignment to better understand motivation of Backbone/frameworks

[Adam Zerner]

I got started with web development a few months ago. I had never gone through the struggles of spaghetti code with JS/jQuery.

Learning Backbone/other frameworks before going through this seems like learning the solution before understanding the problem. I know you talked about the problem a bit, but it doesn't seem like enough to me. Perhaps you could a) talk about it some more and/or b) give us an assignment that forces us to encounter the problems.

[Juan Soto]

This isn't what you are looking for, but take a look at this Udacity course. You do exactly that: Build an spaghetti-code app that gets very annoying to extend, then slowly structure with via MV*, then at the end you look at how you'd use a library to do it. In that course you use Knockout, but you also look at Backbone.

I always thought this book was aimed at those who had been writing unorganized code for some time, so I think adding a whole new section or assignment just to make you write bad code is too much. However, I do agree some sort of short talk or an example of an unorganized project would be useful.

[Adam Zerner]

This isn't what you are looking for, but take a look at this Udacity course.

I will. Thanks!

I always thought this book was aimed at those who had been writing unorganized code for some time

That's understandable.

so I think adding a whole new section or assignment just to make you write bad code is too much

I think that if the section was prefaced properly, people would know whether or not they should skip it, and thus wouldn't really have a downside. I did a coding bootcamp and have seen a lot of people start learning frameworks without having experienced the underlying motivation, so I just see a need for a proper explanation of the underlying motivation.