Liste des Groupes | Revenir à cl c |
On Tue, 28 May 2024 12:33:02 +0200True. My (the obvious?) rule of thumb is that whenever I have to think about wtf Iwas thinking, then I add a comment describing why I did what I did. This often happens when I re-read the code before saving it, but sometimes shortly after that. When I have to think about why I did what I did much later, then it's obviously too late.
Josef Möllers <josef@invalid.invalid> wrote:
On 27.05.24 22:18, Vir Campestris wrote:Probably true.On 27/05/2024 12:51, Josef Möllers wrote:>>>
In my 40+ years of experience in IT/programming (I graduated 1981
from a Dutch polytechnic "HIO" in Computer Science and have
retired in 2022) I have learnt that "works fine" is only part of
the work. Maintainability should be added as well. Even if it is
code written for one's personal use only, it may need some work
later and then it's crucial to have it maintainable.
>
But maybe you think so too,
I agree completely.
>
I learned my lesson a a student with a personal project which I
left for 6 months. When I came back to it I had to comment it
before I could carry on.
You will never have enough comments, even when you consider this rule
;-)
>
And despite that you can very easily have too much (or too many?)
comments.
Les messages affichés proviennent d'usenet.