| Deutsch English Français Italiano |
|
<lbml9jF2iqhU1@mid.individual.net> View for Bookmarking (what is this?) Look up another Usenet article |
Path: ...!news.mixmin.net!news.swapon.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: =?UTF-8?Q?Josef_M=C3=B6llers?= <josef@invalid.invalid> Newsgroups: comp.lang.c Subject: Re: Which newsgroup for json parsing? Date: Tue, 28 May 2024 20:15:15 +0200 Lines: 42 Message-ID: <lbml9jF2iqhU1@mid.individual.net> References: <la1bjoF2anmU1@mid.individual.net> <v25c4k$1lhfu$1@dont-email.me> <lamvvbFb0g2U1@mid.individual.net> <v2aa1g$2q337$1@dont-email.me> <lbjaepFm1vbU1@mid.individual.net> <v32pr7$6p6f$1@dont-email.me> <lblq6uF2jrcU1@mid.individual.net> <20240528144509.00002562@yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Trace: individual.net uXTYxOzKNLFTxK9L/Xd8agDt0i+GxuNPgLdDYS3OPlwRQcuZh1 Cancel-Lock: sha1:FUUo+k+Y3yoZKDlf/ml9/Cz3SOM= sha256:l4pnHL5GfdtCcqwVlu0UtVo5nTbY3wnBHWGPk0lhRCA= User-Agent: Mozilla Thunderbird Content-Language: en-US In-Reply-To: <20240528144509.00002562@yahoo.com> Bytes: 2623 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