Lightning Talk
summary
Forest (that’s with a ph) uses Ember and is powering a product in 10,000 salons aiming for 15,000. A new feature is developed by strict pair programming: 40-minute sessions with a 10-minute break, driver/passenger switching, commit after each slot. An initial attempt at TDD failed so tests land largely at the end. Outcome is faster problem resolution, explicit knowledge transfer from senior to junior, improved team cohesion, one weekly slot keeps momentum, and a Java dev becomes an active Ember contributor.
AI-written summary · about
related talks
27mLightning talks - frontend
33mScaling Frontend: Supercharging Productivity with Dedicated Infrastructure Teams
31mTaming the Beast: Managing a really ambitious codebase
06mLightning Talks - Ember Ghost
01h 02mStability Without Stagnation: Lessons Learned Shipping Ember
21mYehuda Katz and Tom Dale (Tilde Inc.) interviewed at Fluent 2014
59mEmber.js, and why the framework helps you unlocking unprecedented productivity.
59mEmber 2.0: Out-of-the-Box Productivity