Ask HN: How do you fix obscure bugs in large projects?
I know that following clean code/architecture principles and adhering to organization-wide standards can help you navigate and understand the product/code faster, making it easier to identify the source of errors
Still, working on a new and large codebase/project, it often feels like the only way to find solutions to problems is to ask a team member who has more experience with the project. Isn't this a quite ineffective bootleneck?
Imho: What makes some errors hard to solve seems to be a combination of multiple things: traceability, reproducibility, imperfect knowledge and maybe a certain code complexity(which can be tackled following clean code principles etc.)
Is there a more effective way to access the collective knowledge and expertise of people, rather than relying solely on individual team members for solutions to problems?