I am going to start peppering the code with TODO statements (which typically are used to remind yourself to do something) which explain why I did something a certain way, feel free to delete those once you feel like you understand them, or to add your own with questions (in your branch, not on master). We will probably run into merge conflicts doing this, but that's fine, we'll deal with that when it comes.
Alternately, you can generate questions by creating issues, and I will respond to them in the issue tracker. This method would avoid merge conflicts, but I wouldn't worry about it too much. They can be a pain, but we will have to deal with them sooner or later.
I am going to start peppering the code with TODO statements (which typically are used to remind yourself to do something) which explain why I did something a certain way, feel free to delete those once you feel like you understand them, or to add your own with questions (in your branch, not on master). We will probably run into merge conflicts doing this, but that's fine, we'll deal with that when it comes.
Alternately, you can generate questions by creating issues, and I will respond to them in the issue tracker. This method would avoid merge conflicts, but I wouldn't worry about it too much. They can be a pain, but we will have to deal with them sooner or later.