2 ms·
I haven't found a good skimming solution to this. If there's no good documentation, interface, variable naming, or other hint to what it's doing, it either has
by _delirium 15y ago
I haven't found a good skimming solution to this. If there's no good documentation, interface, variable naming, or other hint to what it's doing, it either has to fit a code pattern you recognize easily, or else you have to fall back to mentally tracing through what's going on. If I really need to understand it, I start segmenting the code into sections and adding comments about what it looks like each section is doing. Then you can do a few iterations in bottom-up style. For example, with branches, start out by commenting what every branch does considered in isolation. Then from those comments (now hopefully more transparent than the original code was), see if you can find what pattern a series of tests is doing in aggregate.
- mpg33 15y agofunny you should say skimming...because thats how i have been looking at code and i think it is my main problem...i try scanning the code over and over but get nowhere with it