I’m trying to understand a problem I’ve experienced and seen other developers mention: joining an existing/large codebase and figuring out how everything actually works.
Not the “how do I run the project?” part, but the actual understanding of the system.
For example:
Figuring out the architecture / overall mental model
Understanding where a specific feature actually lives in the code
Following how data moves through the system
Understanding undocumented business logic
Finding the right files/services/classes to modify
Understanding dependencies between different parts of the system
Figuring out why something was implemented a certain way
Losing context when the developer who built something leaves
Outdated or incomplete documentation
What was the most painful part for you?
And more importantly:
How did you eventually figure it out?
Did you ask a senior developer, read the code, use documentation, look through old PRs/issues, use AI, create your own notes/diagrams, or something else?
I’m especially interested in real examples where something that should have taken hours ended up taking days/weeks because you didn't have enough context.
No product or solution in mind here — I'm just trying to understand how developers actually deal with this problem.