Change of questioning is important

I think "How should I start open source contribution" question should change into "How do I understand OS Projects enough to contribute" would help more than ever

One needs a real change from "how to contribute" to "How to navigate huge projects" and in my opinion navigating huge project is one of the longest skill to acquire, relying less on memorization and more on a set tool proficiency and intuition around architecture.

All though you cannot really rely on Devin's explanation of the repository (sometimes you can but at the end you need to be intuitive enough with the architecture so that you can quickly adopt to it)

The intuition part is about intent. One should always start with a concrete goal and trace toward it. If a button triggers an action begin at the UI text or component, then follow the trail until you reach the business logic behind it. Folder structure, filenames and conventions often tell you more than the code itself if you know how to read those signals.

What I try to avoid entirely is reading code at random. I only read code when I am forming a mental model of specific area or answering a specific question. Hence I conclude, one should only be reading code to confirm a specific hypothesis or build a mental model of a feature, not to absorb the entire project at once.