Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: rbowman Newsgroups: comp.os.linux.misc Subject: Re: AI-Based Coding Taking Over Date: 3 Nov 2025 02:28:36 GMT Lines: 17 Message-ID: References: <10e2pfu$l73a$1@dont-email.me> <10e4qbh$16v9t$4@dont-email.me> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Trace: individual.net pfFBuI0iwbkOavPflysS5wsszsjR3q6jE9htdHTUMW1Anqk8Oa Cancel-Lock: sha1:0hRaj2yYn7Bzy3CprrZ7/7bM5us= sha256:Wk2DYYxgR9hyAzdqbki6ilzg3z+a2jMR4fTfLY0Qi6c= User-Agent: Pan/0.162 (Pokrosvk) Xref: csiph.com comp.os.linux.misc:76983 On Sun, 02 Nov 2025 19:30:27 GMT, Charlie Gibbs wrote: > A couple of times I've been faced with nasty bugs that I figured would > be tracked down with an interactive debugger. > But after I found myself playing Twenty Questions with the IDE long > enough, creating project files many times the size of the actualy code > and still not getting to where I could actually do some testing, I gave > up and went back to my old standby of sprinkling printf()s through the > code. (More accurately, I call my homebrewed logging function that > appends messages to a log file.) Yup. The language creators seem intent on coming up with a new term but almost every language has printf, writeln, println, console.log, or some variation and the technique is very portable. The trick is to refine the strategy and remove the statements that aren't useful so you're not looking at a mess.