[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[jbovlaste] Re: defining "debug"
- To: jbovlaste@lojban.org
- Subject: [jbovlaste] Re: defining "debug"
- From: Alaric Snell-Pym <alaric@snell-pym.org.uk>
- Date: Fri, 17 Dec 2010 14:58:21 +0000
- Delivery-date: Fri, 17 Dec 2010 06:59:37 -0800
- Envelope-to: rlpowell@digitalkingdom.org
- In-reply-to: <20101217142814.GC32499@alice.local>
- References: <20101217133000.GA32499@alice.local> <AANLkTinZzGWyActPsETd=-PMGR+xRZhx_xZPDAy6QNJK@mail.gmail.com> <20101217142814.GC32499@alice.local>
- Reply-to: jbovlaste@lojban.org
- Sender: jbovlaste-bounce@lojban.org
- User-agent: Mozilla/5.0 (X11; U; NetBSD amd64; en-US; rv:1.9.1.9) Gecko/20100520 Lightning/1.0b2pre Shredder/3.0.4
On 12/17/10 14:28, .alyn.post. wrote:
> Is there a hint between these two at a more fundamental definition?
>
> If we have a reading fault finder and a computer program fault finder,
> what is a fault finder?
I think there's a worthy distinction between fault *finding*, fault
*diagnosis*, and fault *fixing*; "debug" in computer circles tends to
refer to the latter two, and either users or QA/testers get the first
job :-)
And all of these things can be specialised to computers with a bit of
{sampla}.
ABS
--
Alaric Snell-Pym
http://www.snell-pym.org.uk/alaric/