Continuously Cooking: Our Path to Continuous Delivery


Four years ago, The New York Times launched NYT Cooking, a cooking-specific vertical showcasing 165 years of New York Times Recipes. That Rails Monolith is still in use today, delivering recipes, guides, and how-to videos to millions of users a month.

After three years of legacy and working on a deprecated infrastructure, we were lucky if we shipped once every few weeks, and even then often led to deployment failures. Since then we’ve gone from shipping our monolith with very our fingers crossed to shipping every day with confidence. We’ll look at how we changed our development practices, improved what and how we test, and automated our workflows. We’ll also examine some of the unique enterprise concerns around continuous delivery and how we adapted and evolved our process so our engineering team works in tandem with design, and product to ship as often as possible.

Intended Audience: Developers, DevOps people who are working on complicated/large scale applications and haven’t been able to recognize the benefits of continuous delivery. Audience members should walk away with some actionable takeaways about how they can ship faster, and how they can sell shipping faster to the rest of their organization.

Speaker

scott-feinberg

Scott Feinberg

 

Technical Lead on the 'New York Times' Cooking Product and the CEO of PaperCall.io

Scott is the Technical Lead on the New York Times Cooking Product, a part of our Beta Group. In addition to working

...