> The project is in a scale I never worked with before and ... I don't even know how to debug it. To echo the other people who replied, this isn't a You probl

> The project is in a scale I never worked with before and ... I don't even know how to debug it. To echo the other people who replied, this isn't a You problem. It's normal to feel somewhat lost when thrown into a new codebase. I felt that way when I started at my current job, and three years later I don't feel lost but there are definitely parts that I don't fully understand. Talk to your senior engineers, and/or your on-boarding buddy, and tell them that you're feeling lost and are trying to understand how to debug the problems better, or how to understand what's going on. It will help if you have a specific question (e.g. "how does this code even get executed?", or "where does the data come from that this is using?"). However, a BIG part of being a senior member of the team is being able to help newer people navigate the new codebase. ("New" as in new to the team, new to this code base -- it applies even to engineers with more experience than you.) Consider asking if you can shadow them and watch how THEY debug similar problems, or find where the code + tests is for things. If it's in multiple projects and repos, ask how they know which one to use. Ask them to show you how to get a usable debugger (`ipdb` or `pdb`) prompt in the code you're trying to work on, and how to find (and execute) the tests that exercise its behavior. If it's non-trivial for you to do it, they almost certainly have their preferred way to do it. Also, talk to more than one engineer -- they may have different solutions.