The ideas behind BDD, Specification by Example and Agile acceptance testing are deceivingly simple, but have proved far from easy to implement. Yet most of the complaints online come from misunderstood ideas which lead to misguided attempts. Gojko Adzic will bust the myths around these techniques and show how successful teams all over the world use them to successfully deliver the right stuff using these techniques.
Success can bring many glamorous changes to your company: hiring more employees, getting free coffee, and giving everyone a private jet filled with cash and endangered African predatory cats.
Success can lead to less-glamorous problems, though. As you grow, your team's development environment becomes really important. How long does it take to clone, set up, and boot your apps? Can your employees still be productive on an aging codebase? How can you automate CI, hooks, and other setup for new projects? Is any of this fun anymore?
GitHub ran into these problems as we expanded our team tremendously over the last two years. Let's look at some of the ways we've improved our employees' development environments.
But many of these frameworks forget about the key feature that made the web in the first place: the URL! In this session, you'll see you how Ember's router puts URLs front and center. You'll also see how embracing convention over configuration leads to compact, predictable, and testable code.