🚀 go-pugleaf

On 2/22/2018 4:54 PM, Jorgen Grahn wrote:
> On Thu, 2018-02-22, Peter Flass wrote:
>> Charles Richmond <nume...@aquaporin4.com> wrote:
>>> On 2/21/2018 4:58 PM, ma...@mail.com wrote:
> ...
>>>> I rememebr it being said that medicine is very popular (in
>>>> schools) until the first corpse has to be dissected, and it may be
>>>> the same for computers, when the first debugging has to be done.
>>>
>>> Debugging can be challenging, but *not* as repugnant and
>>> off-putting as cutting up a human body IMO.  Some few actually
>>> enjoy debugging... I've not been in that rare company myself.
>>
>> Sometimes it's fun, or at least satisfying when you get to the "aha
>> moment."
> 
> I like debugging, or more generally troubleshooting.  Apart from the
> stress, and the possibility of failure.
> 
> Things like getting reports of failures from customer sites at the
> other side of the world, gathering the scant evidence, and trying to
> find ways to reproduce the problem.  Or devising ways of getting more
> information.
> 
> On the other hand, I feel uneasy when I'm just writing code and no one
> is going to run it for real until a year later.  The code isn't
> complete until it's in production.
> 

In a book entitled _The Devouring Fungus and Other Tales of the Computer 
Age_, there was a story about a computer that crashed every Tuesday 
around four o'clock.  I was found that the janitor came in at that time 
and plugged in his electric floor buffer...  crashing the computer. 
After things were corrected, the higher-ups were told "it was a buffer 
problem"!!!

Fast forward to a PPoE, where a computer on-site and connected to the 
network... would crash each Thursday at two o'clock.  We got the guy at 
the effected site to sit around on Thursday afternoon to see what 
happened.  Sure enough, the cleaning help came in and plugged the vacuum 
cleaner in the computer's UPS!  Problem solved.

See... interest in computer humor can be helpful!  :-)

-- 
numerist at aquaporin4 dot com