0:008:31

Learnings from the migration of 100k+ lines of Java code

Bárbara Almeida 8:31 2023

A half-finished migration let Java code grow back almost to where it started

Years before this project, an earlier migration had left one component in Java, and when the team finally built a tracker, the Java line count had grown back almost to its starting point. Bárbara Almeida, a software engineer on Cadence's Jasper RTL Apps formal verification tool, shows what it takes to retire hundreds of thousands of lines without freezing feature work. How do you keep a multi-year refactor moving and worth it?

Learn how tracking, mixed-seniority teams and cleanup kept a years-long migration on course

Watch on YouTube

In short

Bárbara Almeida, Software Engineer II at Cadence Design Systems, shares how her team spent several years migrating hundreds of thousands of lines of Java into C++ without stopping feature work. She argues that tracking progress, combining senior and junior developers, and pruning obsolete features make a long refactor both finishable and valuable before it ends.

“Anything that you're not monitoring can easily get out of control.”
“But there is always the indirect benefit for customers when we make the code easier to maintain so we can have less bugs and have faster response times.”

What you will learn

  • Build a tracker before and during a migration so regressions and pace are visible.
  • Plan a gradual migration where senior engineers build the mixed-language bridge first.
  • Use migration tasks to ramp up juniors and new hires through guided work and code reviews.
  • Review each feature before migrating it and deprecate what is no longer used.
  • Explain the indirect customer value of refactoring: easier maintenance, fewer bugs, faster response times.

Key takeaways from the speaker

  • Tracking and inter-team communication are essential tools in a long term project
  • The process is important: opportunity to improve juniors and new hires ramp-up
  • The process is important: exposing code improvements and obsolete features
  • Developer experience (DX) matters in the path for delivering a high quality product

Details

Level
Intermediate
Format
Lightning talk
Technical depth
Introductory technical
For
Early career, Mid-career, Senior individual contributor
Length
8:31
Published
June 2023

Questions this talk answers

Why would a team remove Java from a mostly C++ code base?

Two languages made the tool harder to set up (Java heap sizing), blocked some architecture and performance improvements, and forced developers and tools like linters and sanitizers to cover both languages.

Why is tracking so important in a long migration?

An earlier untracked effort let Java lines grow back almost to their original count; a tracker also shows pace so resources and intermediate goals can be adjusted.

How can developers of different seniority contribute to a migration?

Senior developers built the infrastructure that let C++ and Java coexist, after which people at all levels migrated code, with beginners learning the code base through guidance and code reviews.

Does a migration deliver value before it is finished?

Yes, it exposed future improvements and possible bugs and let the team deprecate unused features instead of migrating them.

Can a large migration run alongside normal feature work?

Yes, the team kept adding features and fixing bugs while migrating slowly but continuously over a few years.

About this talk

It is challenging to decide when it's worth making a code migration and how much effort to allocate. This story is about our successful long-term language migration and our learnings from the results and the process, such as: - Leveraging both senior's and junior's abilities. - The challenges in terms of tracking and communication. - Finding points of improvement and obsolete features. - The resulting improvements in developer experience.

Topics

Related talks

Browse the library