The codebase is just too huge, I just feel lost when trying to read it.
Thanks!
The codebase is just too huge, I just feel lost when trying to read it.
Thanks!
Start with smaller bits of functionality - no one understands a large codebase, certainly when first starting with it.
Concentrate on subsystems that you find interesting, for example:
Once you understand a piece of code, see how it interacts and connects to other parts.
One thing I do is run in debug mode using an interactive debugger, setting a breakpoint in a point of interest and following the code from there and back up the stack.
One way you might approach this is to find a minor (and hopefully interesting) issue from the project's bug tracker. If it's small in scope, fixing it will force you to learn a bite-sized piece of the project (as well as how to build the whole project, which is useful). If its not apparent which bugs are the right size and scope, a post to the developer's mailing list would probably be illuminating.
This way, you'll learn the code better than you would just from eyeballing and make a contribution to boot!