Backbone

During my Hack Reactor prep course, we created a text-based adventure game during a mini-hackathon. At the time, I thought I had a decent understanding of how programing should work. How user events would trigger functions in my code, which in turn would trigger other functions and yet other functions. I didn’t know it at the time, but my code was a jumbled mess. I didn’t have any clue about how to effectively segment my code

This week, we we’re dropped in to Backbone, and were tasked to learn it from the inside. Backbone is the first MVC-link library that I’ve ever worked with. I guess it’ll always have a special place in my heart because of that. This is my first venture into event listeners, and I find the whole concept quite amazing. As we learned the program, the more amazing I found it.

I have a newfound appreciation on the separation of powers that a Model-View-Controller provides. You know which one is responsible for what types of action, and in theory, changes or modifications to part of the process will not cause harm to any other. The modularity of it all is quite amazing to me. I just had to share my thought on the topic.

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.