Tips for Learning a New System and Codebase at a New Job

First, I figure out what problem the code solves. I check the documentation, set up my dev environment, and play around with the software. Understanding the architecture—like whether it's microservices or a client/server model—is crucial. I typically start with smaller bug fixes to get a feel for the codebase before moving on to bigger tasks.

If you have access to LLMs like Copilot, that’s a game changer! You can ask it to highlight key areas in your codebase and help you identify main features and complexities. It’s a helpful tool to kickstart your understanding, but always double-check by running the code yourself.

I’ve found that asking for dedicated time—one to three weeks—to familiarize myself with a new system is essential. It doesn’t matter how good the documentation is; just spending time exploring the code really helps. It can take time to get comfortable, so be patient with yourself!

Don't stress too much! Just take it one day at a time. Start with your HR onboarding, set up your development environment, and then tackle simple tasks. Focusing on completing one task at a time can really alleviate the pressure.

When I take on new code or systems, I usually start by reading through the tests. They give me a good grasp of how the code should function. Then, I like to tinker around using debuggers while running tests to see how the data flows. It really helps clarify how everything works together.