![]() ![]() Go through existing unit tests for functional code, in a similar fashion to above.If not, you've got a puzzle to solve and or an enquiry to make. If it turns out as you expected, you've probably understood the code. Start with an assertion of how you think code will work. Rotate partners amongst team members so knowledge gets spread around. Pair up with someone more familiar with the code base than you, taking turns to be the person coding and the person watching/discussing.Step through code in debug mode to see how it works.However if this is not the case, what can you do to start adding value as quickly as possible? In industry I imagine you'd get an introduction by an experienced programmer. I'm working on what is currently an approx 20k line C++ app & library (Edit: small in the grand scheme of things!). Try to gain insight from class diagrams and uml, if available (and up to date).Pick a feature to develop and learn as you go along.Narrow focus on small sections of code at a time, understanding how they work fully. ![]() Broad try to get a general overview of how everything links together, from the code.Joining an existing team with a large codebase already in place can be daunting. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |