- See if you can pair with someone a few months or a year ahead of you. They'll be new enough to remember what it's like to be new, but experienced enough to gi

- See if you can pair with someone a few months or a year ahead of you. They'll be new enough to remember what it's like to be new, but experienced enough to give you advice. Seniors devs can sometimes be very busy, not approachable, and don't remember what it's like to be new - Just read the entire codebase...I know that's not very popular, or efficient. If it's an enormous codebase, just take it folder-by-folder. Skim large files or things you don't understand. Eventually something will pop out as familiar and you'll notice some patterns. Ask questions about those patterns and see if your intuition is correct. - Figure out what the output is supposed to be. Is it a web app? Get it running locally so you can view it in a browser. Something else? Run the test suite and see what the tests actually do. If it's an embedded project or something that runs on hardware, ask for an experienced dev to introduce you to the hardware and show you how to upload and run builds on it. - Find the entry point for the application. Some sort of main() function, depending on the language. Surrounding it will be some clues as to what the high-level architecture is. Hope that helps!