3 ms·
Also the ability to see when what feature of the code was introduced. That can help a lot with understanding code bases: people seldom comment their code prope
by eru 5y ago
Also the ability to see when what feature of the code was introduced.
That can help a lot with understanding code bases: people seldom comment their code properly, so any context you can get is good.
(In my opinion, really good code can often answer 'what' and 'how' without comments, but it has a hard time answer 'why', and an almost impossible task of answering 'why not'? Ie 'why not' this alternative approach?
Whether the answer to that one is "we tried it and it didn't work" or "we didn't think of it, you are a genius for bringing it up" or something else can be important.)