Talks
Speakers
Events
Topics
Sign in
Home
Talks
Speakers
Events
Topics
Leaderboard
Use
Analytics
Sign in
Suggest modification to this talk
Title
Description
I want to present on why, where, and when backbone would be beneficial to use. We went through the whole motion on our rails project and I want to share in detail how we came about utilizing backbone on our project and hopefully you can too! In the end, implementing Backbone and jasmine led to a cleaner, more organized and better tested code base. Help us caption & translate this video! http://amara.org/v/FGeA/
Date
Summarized using AI?
If this talk's summary was generated by AI, please check this box. A "Summarized using AI" badge will be displayed in the summary tab to indicate that the summary was generated using AI.
Show "Summarized using AI" badge on summary page
Summary
Markdown supported
### Introduction In this presentation at LA RubyConf 2013, Austin Fonacier, a senior software engineer at Spoko, discusses the integration of Backbone.js, Jasmine, and Rails in web development, specifically focusing on a project called Blog Mate. Austin emphasizes the importance of Backbone.js for creating a cleaner, more organized codebase and improving testing. ### Key Points - **Background Information**: Austin shares his experience and highlights his collaboration with Danny on Blog Mate, a project utilizing Rails, Backbone, and Jasmine. He notes his self-proclaimed limitations in JavaScript and Ruby expertise but aims to share his practical experiences. - **Framework Overview**: Austin provides a brief overview of the frameworks: - **Rails**: A Ruby-based MVC framework known for its test-driven development (TDD) and RESTful principles. - **Jasmine**: A behavior-driven development (BDD) framework for testing JavaScript code, resembling RSpec in functionality. - **Backbone.js**: A lightweight JavaScript framework that structures client-side applications, offering models, views, and simplified routing for single-page applications (SPAs). - **Project Challenges**: The team initially faced issues with their JavaScript code, which was becoming unmanageable with bloated files filled with inline jQuery. They noted complications with handling views and ensuring changes in models reflected accurately across the application. - **Team's Transition to Backbone**: Austin explains the decision to adopt Backbone.js after encountering difficulties in maintaining modular and clean code. Backbone's structure allowed them to define dedicated JavaScript classes for each model and view, promoting better organization and interaction. - **Implementation Details**: The talk includes code examples demonstrating the use of Backbone for managing models and views, such as how the save functionality mimics ActiveRecord and how views are structured to handle dynamic frontend updates. - **Benefits Realized**: With Backbone, Austin's team achieved: - Modularized JavaScript, leading to a cleaner codebase and improved performance. - Built-in validation and helper methods, facilitating efficient model management. - Enhanced flexibility in view management, allowing them to structure applications efficiently while handling routes seamlessly. - **Unit Testing with Jasmine**: Austin highlights the critical role of Jasmine in implementing unit tests, helping to avoid issues associated with alert-driven development, further ensuring code integrity. ### Conclusion Austin concludes by reaffirming the effectiveness of Backbone.js as a framework that offers organizational benefits, streamlining development processes and fostering better project stability. He encourages attendees to consider utilizing Backbone in their future projects for cleaner architecture and improved testability. ### Takeaways - Backbone.js enhances code organization and flexibility in JavaScript applications. - Jasmine is crucial for ensuring code reliability through effective testing practices. - Continuous learning and adaptation of frameworks can significantly improve development workflows.
Suggest modifications
Cancel
