From: Nuno Silva <nunojsilva@ist.utl.pt>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Books about making shell scripts and other nifty commands.
Date: Fri, 06 Jun 2025 15:14:11 +0100 [thread overview]
Message-ID: <101ut3j$af1$1@ciao.gmane.io> (raw)
In-Reply-To: 1b1e56cf-ffbc-40af-a4a5-fa3e157d3326@gentoo.org
On 2025-06-05, Eli Schwartz wrote:
> On 6/5/25 12:16 PM, Mark Knecht wrote:
>> <hehe>
>>
>> I sense a certain overriding fear about the future...
>>
>> </hehe>
>
>
> I'm not worried about the future, I'm worried about today, and today's
> users seeking help and getting led astray.
>
>
>> To each his own. I agree with you in general - don't trust AI with
>> anything important. If you prefer then 'trust but verify'.
>
>
> I don't consider AI to provide value enhancement for me at all, for much
> the same reason as described at
>
> https://infosec.exchange/@david_chisnall/113690087142854474
>
> It saves time on writing code. It costs *more* time in debugging subtle
> edge cases. This is a steep disadvantage for a technology that is full
> of questions about legal liability!
>
> Of course, your mileage may vary... if it's only for personal use you
> may not care about legal liability, and if you couldn't write it
> yourself at all then maybe the debugging is worth it.
Edge cases, corner cases, implementation details and non-portable
features are reasons why you'd want to *avoid* "GenAI" for shell
scripting.
I'd say a bit of shell scripting is being aware of what the conditions
to be careful with are. That sounds precisely like the kind of thing at
least some public GenAIs might fail at. Possibly even if you stick to
GNU bash and Linux (which shouldn't be a problem unless you plan on your
scripts being used on other systems).
I can't forget the moment when I got a GenAI telling me how to use
killall to kill processes *by name* in Solaris [1]. That said, maybe
that public model was defective, given it claimed the white side of a
Space Shuttle Orbiter goes *down* on top of a carrier aircraft...
[1] https://social.sdf.org/@njsg/113130981279894435
--
Nuno Silva
next prev parent reply other threads:[~2025-06-06 14:15 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-05 3:49 [gentoo-user] Books about making shell scripts and other nifty commands Dale
2025-06-05 15:32 ` Mark Knecht
2025-06-05 16:02 ` Eli Schwartz
2025-06-05 16:16 ` Mark Knecht
2025-06-05 17:19 ` Eli Schwartz
2025-06-06 14:14 ` Nuno Silva [this message]
2025-06-05 16:59 ` Dale
2025-06-05 17:44 ` eric
2025-06-05 19:50 ` Re[2]: " Stefan Schmiedl
2025-06-06 2:58 ` Dale
2025-06-05 17:03 ` Jay Faulkner
2025-06-05 17:56 ` yahoo
2025-06-05 18:48 ` Arve Barsnes
2025-06-05 19:05 ` Eli Schwartz
2025-06-08 0:09 ` [gentoo-user] " Nuno Silva
2025-06-05 18:33 ` [gentoo-user] " yahoo
2025-06-10 9:39 ` Dale
2025-06-10 10:33 ` Quico Jurado
2025-06-10 14:33 ` Mark Knecht
2025-06-10 15:01 ` Eli Schwartz
2025-06-10 16:24 ` yahoo
2025-06-10 18:12 ` Dale
2025-06-10 18:07 ` Dale
2025-06-10 18:18 ` Quico Jurado
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='101ut3j$af1$1@ciao.gmane.io' \
--to=nunojsilva@ist.utl.pt \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox