Simon Turner wrote:
> On 18 Aug, in article
> <
PM0004C78...@ac8409ec.ipt.aol.com>
See....@aol.com
> "jmfbahciv" wrote:
>
>> Simon Turner wrote:
>> > On 17 Aug, in article
>> > <
PM0004C77...@ac83b7da.ipt.aol.com>
>> >
See....@aol.com "jmfbahciv" wrote:
>> >
>> >> If you don't read replies to speedo's posts, then you have missed some
>> >> very interesting posts.
>> >
>> > I'm well aware of that, and I used to just kill speedo's posts so I
>> > could try to pick out the worthwhile replies; but I found it impossible
>> > to read the replies without also reading (some of) what he had written,
>>
>> I just skip it while I'm scanning the post.
>
> I found I couldn't. Some part of it would catch my eye and I'd find my
> blood pressure rising.
Sounds like a tool to use to learn how to relax. ;-)
>
>> IMO, Morten's write-ups are worth the stress. He would not have done
>> some of them if I hadn't talked with speedo.
>
> That would make an interesting mod to my script: look for long posts by
> non-Rods (esp. Morten) that have a high ratio of new material to quoted
> stuff, and don't mark them as read. Hmmmmm.
Even the short ones. I don't think I've ever seen a post from
Morten that didn't have something new and interesting to me.
>
> (I find wading through 200 lines of quoted material just to find two
> lines of new stuff annoying, too; I wish more people would trim before
> replying!
I have a difficult time trimming because I can't decide which ones aren't
important. But I don't read the angle-bracketed lines unless I need
to refresh my memory about the subject.
> But the old customs are dying out: there's one group I skim
> where the local netiquette has it that trimming posts before replying is
> a Bad Thing, because it makes you look as though you're trying to hide
> something. They have a lot of rather unpleasant arguments in that
> group, which has obviously skewed perceptions over the years.)
Sounds like they need some retraining.
>
>> > Indeed. I'm alarmed by the amount I can't recall about software I wrote
>> > only a few years ago...
>>
>> <grin> TW couldn't remember what he wrote yesterday. OTOH, JMF remembered
>> every line of code and why it was written the way it was written.
>
> Would that I could have JMF's memory.
There was one programmer so used to his ability to recall code that the
programmer expected him to recall someone else's code written after Jim
stopped working for the PDP-10 product line.
> Even with my (in)famous reams of
> comments I still sometimes find myself wondering why I did something in
> a particular way; and to cap it all, recently I accepted a minor feature
> request to some old software and actually got part of the way into the
> job before realising that I'd already implemented the feature when I
> first wrote the code six years ago, but the user hadn't spotted it. 8-/
Did you sit on it and then present after the equivalent time of
implementation? :-) That kind of thing was covered by our writers
so that even the most bizarre user interface would be documented.
A few writers would read our listings to find all the error messages.
/BAH