Changes

*** Why read source code at all?*** Imagine having to fix a bug in a multi-million line program, where do you start?*** Top-down, bottom-up, something else?*** Is adding a feature different from fixing a bug?

* DOs and DON'Ts** DO approach things with optimism. You can do this, don't start by being overwhelmed** DON'T get bogged down in details (at first)** DO open a million tabs, skim through things fast, start to narrow your focus** DON'T try to understand everything** DO formulate questions: questions to research in the code (who calls this? where is this defined?), questions to ask devs** DON'T be afraid to start down different paths in parallel. Walk away when you get frustrated, come at it again from a new angle ** Goal Orientedvs. For Enjoyment