Path: ...!local-1.nntp.ord.giganews.com!Xl.tags.giganews.com!local-2.nntp.ord.giganews.com!nntp.earthlink.com!news.earthlink.com.POSTED!not-for-mail
NNTP-Posting-Date: Mon, 30 Sep 2024 07:40:49 +0000
Subject: Re: Can't Avoid That Shit Rust - Even On Gentoo
Newsgroups: comp.os.linux.advocacy,comp.os.linux.misc
References: <pan$96411$d204da43$cc34bb91$1fe98651@linux.rocks>
 <5mqdnZuGq4lgwm_7nZ2dnZfqnPSdnZ2d@earthlink.com>
 <9tDIO.25203$afc4.21891@fx42.iad> <llgvjcF5rlhU3@mid.individual.net>
 <59JIO.96321$WtV9.10707@fx10.iad> <vd8bou$15h6g$2@dont-email.me>
 <18udnd3mEtEGfGX7nZ2dnZfqnPGdnZ2d@earthlink.com>
 <vdap5d$1kp35$4@dont-email.me>
 <fcKcnSXE3MsnqWf7nZ2dnZfqnPudnZ2d@earthlink.com>
 <D0rKO.165127$EEm7.5633@fx16.iad>
From: "186282@ud0s4.net" <186283@ud0s4.net>
Organization: wokiesux
Date: Mon, 30 Sep 2024 03:40:49 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101
 Thunderbird/78.13.0
MIME-Version: 1.0
In-Reply-To: <D0rKO.165127$EEm7.5633@fx16.iad>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Message-ID: <oi2dncHrnMKcy2f7nZ2dnZfqn_GdnZ2d@earthlink.com>
Lines: 25
X-Usenet-Provider: http://www.giganews.com
NNTP-Posting-Host: 99.101.150.97
X-Trace: sv3-MfKMXyHd4qr5zYY+SiTgJToGIUu05LPPUdRl0GiUYn6Qt6JAgQaZUALVDEsCx+RTQMAnuu1KGW/+oeb!tlgWFxQi7NAakAK55RK+RrHVtdAGbPTxG4uokO6gaKOsGxXF/DJ2aH5lGk1OXq2JWGGCrTfe+i+a!XtHcsikf3MmjFL0J10P/
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
X-Postfilter: 1.3.40
Bytes: 2577

On 9/30/24 1:52 AM, Charlie Gibbs wrote:
> On 2024-09-30, 186282@ud0s4.net <186283@ud0s4.net> wrote:
> 
>>     I've occasionally done that with Python.
>>
>>     HOWEVER, the FUTURE readability suffers considerably.
>>
>>     IMHO, write code so YOU can go back to it like five
>>     years later and actually grasp what you did and why.
>>     Overly-complex code, and 'feature creep' RUIN pgms.
> 
> Yup.  Be generous with comments, and write them in plain
> English, not some cryptic set of abbreviations that nobody
> else would understand.  And remember that those comments
> aren't necessarily for someone else - they're for you
> six months from now, when you've forgotten why you wrote
> what you did.

   All my work had more comments than code ... almost
   every line explained and 'concept' stuff above
   every function.

   However 5+ years on, STILL kinda difficult to
   get the whole groove sometimes. This is not
   so good, but it seems COMMON.