CppCon 2018:H. Wright “Large-Scale Changes at Google: Lessons Learned From 5 Yrs of Mass Migrations”

Hyrum Wright “Large-Scale Changes at Google: Lessons Learned From Five Years of Mass Migrations”
—
—
Google has one of the largest single C++ codebases on the planet, yet is able to continually update both core libraries and the code which uses them. In this talk, I'll share many of the lessons we've learned across more than five years of doing these kinds of migrations, including:
* Why should you migrate in the first place?
* How hard can it really be?
* What happens when a change can't be done atomically?

I'll also talk about the myriad ways that such a process can go wrong, using various migrations we've done internal to Google to illustrate. In doing so, I'll also point out how you can structure your infrastructure and tooling to enable a successful large-scale change process within your organization.
—
Hyrum Wright, Google
Software Engineer

Hyrum Wright hates C++ less than the rest of the programming languages he's worked with, and works on large-scale change infrastructure at Google. He writes programs to rewrite other programs, and will eventually put himself out of a job. In a former life, he was an author of Apache Subversion, and still retains membership in the Apache Software Foundation. Hyrum enjoys cycling, but didn't bring a bike to Seattle.
—

*-----*
*-----*

[lethern]

I don't like the setter/getter example, I'd even say that it doesn't solve anything, in my view. If you change your internal type from int to int64, or say, from int to double, you have to change your getter/setter too, and that will break code the same way as if you didn't have setters/getters at all, imho

[roberthickman]

JAI can dump the AST back to a program.