4 ms·
The easiest way I've found is to try to find out how a specific piece of functionality works. Try to modify it in some small way -- that way you can test your
by mikekchar 8y ago
The easiest way I've found is to try to find out how a specific piece of functionality works. Try to modify it in some small way -- that way you can test your understanding. It's a bit like putting together a big puzzle. You just take it one piece at a time -- but try to break it up by functionality so that you are forced to see how everything fits together. Often it's great to try to write tests or fix bugs. Again, this gives you some focus. But don't expect to learn it quickly. It takes time for things to sink in.
- revskill 8y agoGood points. It's also the way to incrementally adopt unit tests to existing codebase.
- krishoog 8y agoIn addition: if other people are working on the code base, I find it very insightful to first read what task/issue they are working on and then look at the commit they made. I then try to see if I understand why the commit implements the described task or solves the issue. You can do the same if nobody is actively working on the code but you have the history in source control.