7 ms·

When you revisit old code, does it seem like a room in a house? Does it make you think of other code? (code nearby, or maybe code you write around the same ti

• oscargrouch 7y ago
  I've worked with lot of different codebases in my life, but nothing ever like the one im dealing now, so thats why i had no idea how/if i could handle it. Of course theres a erosion process if you dont touch that piece of code for more than 1 year, and it happens with a codebase of that side, but the 'partial data' is is still there, and with a couple of minutes dealing with it, you recover the information. Its better when you shape the code yourself.. when you lay down the objects, methods, etc.. But this also works great with code i've happen to just use. For the architecture and where things are.. be it files, methods, or where i could find something i want.. there were no lost. I feel i need this partial recovery process mostly for codebases with 2 or more years, and the lost is minimal and can be recovered quickly. Now being more specific over your question, for me it fells more like a map, smaller maps or trees connected to top-level maps... But yes, it feels a little like rooms as in a quadtree, where you need to specialize and ignore the other parts of the tree for a bit, much like the occlusion/visibility process that algorithm gives. By the way is great that you have used this analogy, because this is also part of an observation i've had about laying down the information for a specific goal i have in mind. I cant wait to experiment with this as soon as i finish this thing im working on, to see if its really cool as my intuition is telling me..