From: Stuff Received <stuff@riddermarkfarm.ca>
To: coff@tuhs.org
Subject: [COFF] Re: The era of general purpose computing (Re: AIX moved into maintainance mode (COFFed)
Date: Sun, 22 Jan 2023 10:40:27 -0500 [thread overview]
Message-ID: <dc5776cc-6be0-965a-f696-eebf7bad73e5@riddermarkfarm.ca> (raw)
In-Reply-To: <FD266D9F-AB04-4F8E-9F1C-FFCF7DEAA343@pobox.com>
On 2023-01-22 00:23, David Arnold wrote (in part):
> I’ve played with ChatGPT, and the first 10 minutes were a bit
> confronting. But the remainder of the hour or so I played
> overcame my initial concerns.
>
> It’s amazing what can be done, especially with Javascript or
> Python, when you ask for something that’s fairly simple to
> define, and in a common application area. You can get reasonable
> code, refine it, ask for an altered approach, etc. It’s probably
> quicker than writing it yourself, especially if you’re not
> intimately familiar with the library being used (or even the
> language).
>
> But … it pretty quickly becomes clear that there’s no semantic
> understanding of what’s being done behind it. And unless you
> specify what you want in pretty minute detail, the output is
> unlikely to be what you want.
The comment by Derek Jones
(https://shape-of-code.com/2023/01/15/coding-mistakes-made-by-chatgtp/)
may be of interest here.
N.
next prev parent reply other threads:[~2023-01-22 15:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <202301180943.30I9hrOw030485@freefriends.org>
[not found] ` <202301181513.30IFDDUJ015224@freefriends.org>
[not found] ` <20230118151446.GD2964@mcvoy.com>
[not found] ` <202301190802.30J82KwQ025718@freefriends.org>
[not found] ` <20230119150434.GA626@mcvoy.com>
[not found] ` <CANCZdfqwEaKtfAyjE+2eQtEsKOjn0xtXgx-6KT_V0WgGC3YDGg@mail.gmail.com>
[not found] ` <alpine.DEB.2.21.2301191157040.522@sd-119843.dedibox.fr>
[not found] ` <CAP2nic2h1cxi-iXDty8mZ+oXs89wGRDuHOmD=nxjWAPRvU1teA@mail.gmail.com>
[not found] ` <BDDE0D7F-E886-4E38-83AE-F7542976060A@iitbombay.org>
[not found] ` <7cc2b7c5-5e98-9299-4fa8-a477fbf4ff77@makerlisp.com>
[not found] ` <CAD2gp_QXbtVZHb=VN1QL7bJAVqRj4S5C-y5uMSQh704-4GH3wQ@mail.gmail.com>
[not found] ` <75cfc721-a662-ddea-1188-767462d747ae@makerlisp.com>
[not found] ` <202301211812.30LICtSl021234@freefriends.org>
[not found] ` <396750c7-6fc8-9b15-5e68-9f569718ba2e@makerlisp.com>
2023-01-21 21:12 ` [COFF] Re: The era of general purpose computing (Re: AIX moved into maintainance mode segaloco via COFF
2023-01-22 5:23 ` [COFF] Re: [TUHS] The era of general purpose computing (Re: AIX moved into maintainance mode (COFFed) David Arnold
2023-01-22 15:40 ` Stuff Received [this message]
2023-01-22 16:38 ` [COFF] " segaloco via COFF
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=dc5776cc-6be0-965a-f696-eebf7bad73e5@riddermarkfarm.ca \
--to=stuff@riddermarkfarm.ca \
--cc=coff@tuhs.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;
as well as URLs for NNTP newsgroup(s).