Berlin

November 4 & 5, 2024

New York

September 4 & 5, 2024

London

June 16 & 17, 2025

Why onboarding to a company's legacy codebase sucks, and how to make it work for your team

Shanea Leven discusses the history and context of the problems that plague codebase onboarding. And with problems come solutions such as tips and tools that make it easier for engineers to onboard a legacy codebase.

Register or log in to access this video

Create an account to access our free engineering leadership content, free online events and to receive our weekly email newsletter. We will also keep you up to date with LeadDev events.

Register with google

We have linked your account and just need a few more details to complete your registration:

Terms and conditions

 

 

Enter your email address to reset your password.

 

A link has been emailed to you - check your inbox.



Don't have an account? Click here to register
March 09, 2023

It’s not uncommon to hear from engineers and their managers on how difficult it is to onboard a company’s legacy codebase.

We’ve all heard horror stories about untangling spaghetti code and spending hours on self onboarding just to realize that you still have no idea on what areas require the most attention. This kind of experience creates hesitation and friction for new engineers to review code and requires more resources from engineering managers to onboard new engineers.

In this talk, I will be discussing the history and context of the problems that plague codebase onboarding. And with problems comes solutions such as tips and tools that make it easier for engineers to onboard a legacy codebase. My goal for more senior engineering leaders is to provide a solution that helps deliver more value and make engineering teams more efficient during the current economic reality that we’re facing.