Well said. I am currently working my way through an unfamiliar codebase and even as a mid-career developer, I find it intimidating and inconvenient to continual

Well said. I am currently working my way through an unfamiliar codebase and even as a mid-career developer, I find it intimidating and inconvenient to continually ask for help over slack for "basic questions". People say the answer is to go deep and gain expertise, but in my experience you need to reach a certain escape velocity with the codebase before that kind of spelunking becomes valuable learning experiences and not just a confusing and messy waste of time. You need either: * Documentation that is up to date and answers not just technical details but the "why" behind the architecture. Something that shows you where to focus and where the frontier is. * Defined, limited scope (at first). Scoping yourself to the entire codebase is a good way to become an expert in nothing. You need a foothold where you can gain expertise and give yourself a jumping off point to adjacent areas. The latter is easier to accomplish than convincing everyone to write pages of docs that don't exist.