Tern Stories

Code migration is transforming how modern software is built, but few are talking about the risks that come with it.

In this episode, we explore how code migration is reshaping API security, infrastructure, and the very foundations of enterprise development.

From GraphQL to AI-driven architecture, we uncover what’s really happening behind the buzzwords, and why companies are struggling to keep their systems secure during massive migrations.

Whether you’re a developer, architect, or engineering leader, this conversation reveals the hidden trade-offs of code migration, the growing complexity it introduces, and how to protect your systems before it’s too late.

If you’re planning your next modernization effort or already knee-deep in legacy refactors, this is a must-watch. We break down practical lessons, real-world examples, and strategies to make code migration work for you, not against you.

Get Tern Stories in your inbox: https://tern.sh/youtube

In this episode, we dive into Snapchat’s bold code migration, a project that reshaped the way their app runs at scale.

This code migration wasn’t just about rewriting code, it was about survival, speed, and creating a leaner system that could handle hundreds of millions of users.

You’ll hear how the team faced challenges like supporting long-dead features, rebuilding APIs bug-for-bug, and even migrating conversations instead of entire users.

These behind-the-scenes stories reveal the hidden complexity of a massive code migration and the lessons that can help any engineering team facing similar challenges.

Whether you’re an engineer, a founder, or just fascinated by how the biggest apps in the world evolve, this deep dive into code migration will show you what it really takes to pull off a technical transformation at scale.

Connect with Ben Hollis ➡️ https://stately.cloud/

Get Tern Stories in your inbox: ➡️ https://tern.sh/youtube

Code migration is one of the toughest challenges engineers face at scale. In this episode, we dive deep into a real-world code migration that powered millions of queries daily.

You’ll hear how Sourcegraph rebuilt their core parser, the testing strategies that prevented disasters, and why “unglamorous engineering” is often the work that matters most. From differential testing to temporary safety nets, this story shows how code migration can be done without breaking everything.

Whether you’re planning a refactor, facing a large-scale rewrite, or just curious about engineering under pressure, the lessons here will help you approach your next code migration with confidence.

Get Tern Stories in your inbox: https://tern.sh/youtube

Code migration isn’t hard because the code is complex, it’s hard because the real problems only reveal themselves once you’re already in the middle of it.

In this episode, I break down why code migration projects so often drag on for months or years, and how AI can change that story completely.

From Stripe and Pinterest to Airbnb, Zapier, Twitter, and Slack, you’ll see how teams faced huge migration challenges, and how better planning, faster learning, and smarter communication turned the tide.

I’ll share lessons on why every code migration is unique, how small overlooked details can derail entire timelines, and how AI can uncover those issues before they blow up.

If you want your next code migration to feel less like chaos and more like a smooth, predictable process, this episode will give you the roadmap.

Get Tern Stories in your inbox: https://tern.sh/youtube

When a critical code migration goes wrong, the stakes can be nothing short of catastrophic.

In this episode, we dive into the code migration that almost brought one of the world’s largest social platforms to its knees.

You’ll hear the inside story of how engineers raced against time to prevent total failure, the technical hurdles that made this code migration uniquely challenging, and the high-pressure decisions that determined success or disaster.

We break down the lessons learned, the strategies that worked, and how these insights can prepare you for your own future code migration.

If you’ve ever wondered what happens when code migration becomes a matter of survival, this is the episode you can’t afford to miss.

Get Tern Stories in your inbox: https://tern.sh/youtube

Code migration isn’t just a technical task, it’s a minefield.

In this episode, we dive into a real-world code migration story from Slack that uncovered terrifying truths lurking deep in the system.

From multi-user duplication chaos to security incidents hiding in plain sight, this is code migration at its most high-stakes.

You’ll hear how Slack’s “Storm Chasers” team tackled six massive code migration prongs, rewrote critical data models, and avoided taking down the entire platform, all while operating at enterprise scale.

If you’ve ever touched a legacy system, dealt with user provisioning, or tried to clean up a years-old data mess, this is your masterclass in what code migration really looks like.

Whether you’re a staff engineer, EM, or just trying to survive your company’s next code migration, don’t miss this.

Get Tern Stories in your inbox: https://tern.sh/youtube

Connect with Sarah:   linkedin.com/sarah-mann-14758844  

Code migration sounds like a technical task, but it’s a strategic minefield.

In this episode, we explore how code migration projects fail not because of bugs, but because of broken decision-making and unclear architecture.

You’ll hear about raw stories from engineers at Slack, Datadog, and other world-class teams who’ve battled through the chaos of code migration under pressure.

If you’re relying on AI to do the thinking for you, this episode will make you rethink everything.

Whether you’re planning a rewrite or deep in the trenches, you’ll learn how to survive your next code migration, and maybe even lead one right.

Get Tern Stories in your inbox: https://tern.sh/youtube

Code migration sounds like a technical task, but it’s a strategic minefield.

In this episode, we explore how code migration projects fail not because of bugs, but because of broken decision-making and unclear architecture.

You’ll hear about raw stories from engineers at Slack, Datadog, and other world-class teams who’ve battled through the chaos of code migration under pressure.

If you’re relying on AI to do the thinking for you, this episode will make you rethink everything.

Whether you’re planning a rewrite or deep in the trenches, you’ll learn how to survive your next code migration, and maybe even lead one right.

Get Tern Stories in your inbox: https://tern.sh/youtube

Code migration doesn’t have to be slow and painful. In this episode, Madeline and I break down a proven method to speed up your code migration process without sacrificing code quality or stability.

You’ll learn actionable insights from a real-world team who successfully tackled code migration at scale, and did it faster than most thought possible!

If you’re planning a code migration, currently in one, or trying to avoid the common pitfalls, this episode is packed with the perspective you need.

Let's break down a real world example with Madeline, which is a smarter way to approach your code migration strategy and accelerate delivery without cutting corners!

Get Tern Stories in your inbox: https://tern.sh/youtube

Connect with Madeline!

➡️ https://www.linkedin.com/in/madelineshortt/

Tom Elliott joined Yext in 2015 as an iOS developer. Within a year, both his mobile projects were canceled.

But Tom's career crisis was nothing compared to what was happening with Yext's infrastructure. 

The company was hitting the limits of homegrown tools built by ex-Google engineers who had recreated their own version of Borg called Khan. It worked when Yext was small. Now they were running thousands of microservices—Tom calculated they had a higher microservice-to-employee ratio than Uber.

The real breaking point? Server upgrades. Every time the infrastructure team needed to upgrade a machine, they had to manually edit code to move services off, do the upgrade, then edit code again to move everything back.

"Everything was manually configured as to where things lay," Tom recalls.

Khan had been built by "one or two people" as a coalition of the willing.

Now Yext had grown past 20 teams, and adding the features they desperately needed—like automatic workload migration—would require massive investment in a homegrown system.

---

Get Tern Stories in your inbox: https://tern.sh/youtube

Connect with Tom! : https://www.ocuroot.com/