Title: My question is pretty straightforward: how do you, hacker news enthusiast, familiarize yourself with a new codebase? Obviously your answer is going to be contingent on the kind of work that you do.<p>Some background: What&#x27;s motivating me to ask is that I am flirting with the idea of trying to add a couple of features to SlickGrid (https:&#x2F;&#x2F;github.com&#x2F;mleibman&#x2F;SlickGrid), Michael Leibman&#x27;s phenomenal javascript grid widget. Unfortunately Leibman got busy and isn&#x27;t actively supporting it anymore.<p>The codebase is something like 8k lines of javascript, so it&#x27;s not ludicrously big, but I&#x27;m kind of intimidated thinking about trying to make sense of it. My first strategy is just to open up important-looking javascript files (slick.core.js, slick.grid.js) and read through for comprehension. This seems like a pretty slow way to build a mental model of the code, though. Some features I want to implement are 1. an ajax data source that doesn&#x27;t require paging, and 2. frozen columns. Someone else has implemented a buggy version of frozen columns (and since abandoned the project), and I might like to use it, but I can&#x27;t tell if it&#x27;s buggy because it&#x27;s a hard problem, or because their implementation strategy was poor (or both!). So at the moment I can&#x27;t evaluate if I should implement my own, or try to fix the issues with theirs.<p>Picking up other people&#x27;s code seems to be one of the harder tasks developers face, as evidenced by how much code gets abandoned, so I wondered if the voices of experience on here could point me in the right direction, either by talking about this problem in particular, or more generally, how you build knowledge about a new codebase.<p>Thanks!
Upvote: