[baq]

ripgrep

But to not leave a one word answer, start searching for a feature you know about and look around from where you find it. It might help to add a super small feature yourself - when it finally works, you’ll have some idea of how the code is structured and will be able to infer where other features would live if they were there. (That might take a bit more than one addition ;))

In chromium’s case, what you’re trying to do is more like reverse engineering… I’d start with a debugger.

[pizza]

Yup

- ripgrep when you know what you’re looking for already

- “find usages” when you’ve stumbled upon something interesting sounding, and want to see where it gets invoked (jetbrains ides)

- (gist.)github.com/search when you want to see how others have used some api