Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.misc > #81652
| Message-ID | <697a8cfb@news.ausics.net> (permalink) |
|---|---|
| From | not@telling.you.invalid (Computer Nerd Kev) |
| Subject | Re: The Value of a 2nd Look At Code |
| Newsgroups | comp.os.linux.misc |
| References | (1 earlier) <6975f968$0$28050$426a74cc@news.free.fr> <3csdR.1398925$H7H.1265376@fx13.iad> <Sqidna7J3815S-v0nZ2dnZfqnPWdnZ2d@giganews.com> <20260126081836.000048f9@gmail.com> <10l9r7r$o26j$1@news1.tnib.de> |
| Date | 2026-01-29 08:26 +1000 |
| Organization | Ausics - https://newsgroups.ausics.net |
Marc Haber <mh+usenetspam1118@zugschl.us> wrote: > John Ames <commodorejohn@gmail.com> wrote: >>On Sun, 25 Jan 2026 21:52:08 -0500 >>c186282 <c186282@nnada.net> wrote: >>> I suspect that stuff like programs may leave waking consciousness, >>> but somewhere deep down keep some little processes running. Then, >>> when you go back to it after awhile, new and better approaches and >>> tweaks seem to come easily. >> >>Absolutely. Our lead developer at $EMPLOYER has often related stories >>of working on a problem for hours or days, leaving off and going to >>bed, and waking up the next morning with the answer waiting for him. > > That often happens, yes. But I also have the situation when I go to > bed with an open issue that it takes me too long to get to sleep > because I keep pondering about the issue. I usually find the obvious answer while lying in bed, and go to sleep entirely satisfied. Then after working on it the next day I discover that in my tiredness I'd just forgotten most of the constraints that made the problem difficult in the first place. Good for sleep, bad for problem solving (especially if I don't remember in the morning either and start extensively redesigning things). > It also helps to explain the problem so someone. MIT used to have a > teddy bear in next to the door to the user helldesk, people had to > explain their problem to the bear before being allowed in. People tell > that many people stopped right in their explanation and went back to > their console. Most times I go to start a technical topic on Usenet I realise the answer by the time I've got to the end of writing it and just keep it as a private note. > In the last months I made the experience that is also helps to explain > the issue to an LLM. Well I guess that's the modern version of what I do. -- __ __ #_ < |\| |< _#
Back to comp.os.linux.misc | Previous | Next — Previous in thread | Next in thread | Find similar
The Value of a 2nd Look At Code c186282 <c186282@nnada.net> - 2026-01-24 21:55 -0500
Re: The Value of a 2nd Look At Code Stéphane CARPENTIER <sc@fiat-linux.fr> - 2026-01-25 11:07 +0000
Re: The Value of a 2nd Look At Code Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-01-25 17:14 +0000
Re: The Value of a 2nd Look At Code c186282 <c186282@nnada.net> - 2026-01-25 21:52 -0500
Re: The Value of a 2nd Look At Code John Ames <commodorejohn@gmail.com> - 2026-01-26 08:18 -0800
Re: The Value of a 2nd Look At Code c186282 <c186282@nnada.net> - 2026-01-26 13:04 -0500
Re: The Value of a 2nd Look At Code Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-01-27 01:26 +0000
Re: The Value of a 2nd Look At Code Marc Haber <mh+usenetspam1118@zugschl.us> - 2026-01-27 08:58 +0100
Re: The Value of a 2nd Look At Code not@telling.you.invalid (Computer Nerd Kev) - 2026-01-29 08:26 +1000
Re: The Value of a 2nd Look At Code c186282 <c186282@nnada.net> - 2026-01-28 23:10 -0500
Re: The Value of a 2nd Look At Code Stéphane CARPENTIER <sc@fiat-linux.fr> - 2026-01-31 10:26 +0000
Re: The Value of a 2nd Look At Code Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-01-31 19:39 +0000
Re: The Value of a 2nd Look At Code c186282 <c186282@nnada.net> - 2026-01-31 23:57 -0500
Re: The Value of a 2nd Look At Code Chris Ahlstrom <OFeem1987@teleworm.us> - 2026-01-26 07:09 -0500
Re: The Value of a 2nd Look At Code Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-01-27 01:26 +0000
Re: The Value of a 2nd Look At Code c186282 <c186282@nnada.net> - 2026-01-27 01:23 -0500
Re: The Value of a 2nd Look At Code The Natural Philosopher <tnp@invalid.invalid> - 2026-01-27 10:24 +0000
Re: The Value of a 2nd Look At Code Stéphane CARPENTIER <sc@fiat-linux.fr> - 2026-01-31 10:16 +0000
Re: The Value of a 2nd Look At Code rbowman <bowman@montana.com> - 2026-02-01 03:04 +0000
Re: The Value of a 2nd Look At Code John Ames <commodorejohn@gmail.com> - 2026-02-02 08:44 -0800
Re: The Value of a 2nd Look At Code rbowman <bowman@montana.com> - 2026-02-02 21:27 +0000
Re: The Value of a 2nd Look At Code c186282 <c186282@nnada.net> - 2026-02-02 21:06 -0500
Re: The Value of a 2nd Look At Code ram@zedat.fu-berlin.de (Stefan Ram) - 2026-01-25 17:53 +0000
Re: The Value of a 2nd Look At Code c186282 <c186282@nnada.net> - 2026-01-25 21:52 -0500
Re: The Value of a 2nd Look At Code Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-01-25 19:16 +0000
Re: The Value of a 2nd Look At Code c186282 <c186282@nnada.net> - 2026-01-25 21:58 -0500
Re: The Value of a 2nd Look At Code Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-01-26 04:33 +0000
Re: The Value of a 2nd Look At Code Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-01-26 04:46 +0000
Re: The Value of a 2nd Look At Code c186282 <c186282@nnada.net> - 2026-01-26 01:05 -0500
Re: The Value of a 2nd Look At Code Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-01-27 01:26 +0000
Re: The Value of a 2nd Look At Code Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-01-27 05:13 +0000
Re: The Value of a 2nd Look At Code c186282 <c186282@nnada.net> - 2026-01-26 00:44 -0500
Re: The Value of a 2nd Look At Code Chris Ahlstrom <OFeem1987@teleworm.us> - 2026-01-26 07:11 -0500
csiph-web