Sujet : Re: Which newsgroup for json parsing?
De : josef (at) *nospam* invalid.invalid (Josef Möllers)
Groupes : comp.lang.cDate : 28. May 2024, 19:15:15
Autres entêtes
Message-ID : <lbml9jF2iqhU1@mid.individual.net>
References : 1 2 3 4 5 6 7 8
User-Agent : Mozilla Thunderbird
On 28.05.24 13:45, Michael S wrote:
On Tue, 28 May 2024 12:33:02 +0200
Josef Möllers <josef@invalid.invalid> wrote:
On 27.05.24 22:18, Vir Campestris wrote:
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
;-)
>
Probably true.
And despite that you can very easily have too much (or too many?)
comments.
True. 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.
A remedy against too much/many comment(s) is to write some thorough documentation.
And, also, don't forget boilerplates for functions!
Josef