Message-ID: <6ab7764c@news.ausics.net> From: Computer Nerd Kev Subject: Re: More Lazy(?) Programmers Are Seduced By AI Newsgroups: comp.os.linux.misc References: <18d7bd7e3b290a97$107$2277794$802601b3@news.usenetexpress.com> <11911vm$1vull$1@dont-email.me> <11917rh$227v3$1@dont-email.me> <6ab441ba@news.ausics.net> <1192sh5$2ikqk$1@dont-email.me> User-Agent: tin/2.6.5-20251224 ("Glenury") (Linux/2.4.31 (i686)) NNTP-Posting-Host: news.ausics.net Date: 26 Sep 2026 17:37:48 +1000 Organization: Ausics - https://newsgroups.ausics.net Lines: 20 X-Complaints: abuse@ausics.net Path: csiph.com!news.bbs.nz!news.ausics.net!not-for-mail Xref: csiph.com comp.os.linux.misc:92188 John Bokma wrote: > On 23/09/2026 23:16, Computer Nerd Kev wrote: >> Now what would help me a lot is an AI that can immediately answer >> practical debugging questions like "why did that seg. fault >> happen just then?". > > Again, in my experience, it's quite good at such practical debugging > questions. To answer such questions without doing all the work for it in order to explain all the details (like how after spending an hour or two writing a detailed question about a problem, eg. for posting to a newsgroup, I've often worked out the answer by myself by then anyway), the AI would need to be integrated with the execution environment so it can see what exact inputs caused "that seg. fault". -- __ __ #_ < |\| |< _#