3 ms·
You have to just dive in and change something and then build/run it. Ie you have an expectation, that if you change A then A' will happen. Make the change, bu
by keeptrying 15y ago
You have to just dive in and change something and then build/run it.
Ie you have an expectation, that if you change A then A' will happen.
Make the change, build and test it. If A' does happen then make a bigger change B with the expectation that B' will happen.
Again build and test this. Soon you'll find that either B', C' or D' doesnt happen and then you'll have to debug it.
This is the quickest and fastest way to really learn the codebase IMHO.
Passively looking at files is not going to help. And its just a big waste of time.
Now doing this will be painful but its better to go through the pain now rather than when you have a customer breathing down your neck for a fix.