Timeline for How do you dive into large code bases?
Current License: CC BY-SA 2.5
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 30, 2014 at 1:54 | comment | added | smwikipedia | @ErickRobertson ...and he is not an asshole. | |
| Apr 11, 2014 at 14:31 | comment | added | Erick Robertson | This of course assumes that the author of the code is available. | |
| Nov 16, 2010 at 15:49 | comment | added | PeterAllenWebb | +1 For asking a human. And don't be afraid to sound stupid. Tell them every assumption you have made about the code, and every conclusion you have come to about how it works and what it does. They will inform you that you are incorrect. This small injury to your ego will save you so many hours in the long run that your colleagues may come to regard you as a near-deity. | |
| Oct 26, 2010 at 12:17 | comment | added | poseid | the power of communication is often underestimated | |
| Sep 22, 2010 at 22:29 | comment | added | Mason Wheeler | How do you code an elephant? One byte at a time! | |
| Sep 22, 2010 at 22:09 | history | answered | user2567 | CC BY-SA 2.5 |