Reading code for large systems is rarely fun. I usually start with a specific objective, a bug or feature, to teach myself the system. I root around until I a

Reading code for large systems is rarely fun. I usually start with a specific objective, a bug or feature, to teach myself the system. I root around until I arrive at a solution. The first bug is expensive, but they become cheaper as I learn. I have tried systematic top to bottom examination, but I find my mind quickly turns to glue. Good tools are essential. If you are programming Java, use eclipse. I hated it for the first year, but now I tolerate it. Whatever your language, use its IDE. I am also partial to UltraEdit. Write some good tools. I wrote a version of unix find for Windows among other things. If you want code that's fun to read try the Python Cookbook. http://code.activestate.com/recipes/langs/python/ http://code.activestate.com/recipes/langs/python/ is a good resource.