News for hackers. Stuff that matters.
Re:Interesting Codebases by markpapadakis on Monday October 02, 2017 @06:50AM (#15382920)
For what it’s worth, this is how I usually go about exploring codebases ( I am the author of that blog post ).

I either have something specific in mind that I want to understand, e.g in the case of Seastar, I wanted to understand their reactor design and implementation, so I locate the respective file(s) that implement them and I start from there, and then I just branch out to other files -- I usually keep multiple vim windows open, and I take notes.

When I am not looking for a specific answer, I choose a directory, and then I sort its files by size (e.g ls -lShr *.{h,cpp,hh,cc,java} ). I usually sort by file size in descending order(smallest first), but some times it makes more sense to sort by largest file first, and I start from there. I still map my way around, and if something stands out, I open the respective file in another vim window/tab, and look it up, and then continue with the previous file.

Re:Interesting Codebases by baby on Monday October 02, 2017 @07:32AM (#15383063)
You can also make a git script to check what files are the most modified.

I also have a script that checks what are the most crypto-y file in a directory.

Re:Interesting Codebases by dgellow on Monday October 02, 2017 @08:09AM (#15383208)
> I also have a script that checks what are the most crypto-y file in a directory.

Could you share it? :)