Re: [ALUG] a weird network configuration, does this make any sense at all?
runlevel ten wrote:
On Tue, Nov 10, 2009 at 11:22 AM, <steve-ALUG@hst.me.uk <mailto:steve-ALUG@hst.me.uk>> wrote:
On the other hand, the adage "If it aint broke, don't fix it" is often relevant! :-) Steve
The trouble is, there are many people in this world who use that phrase to mean "It is broke, but let's not fix it until it stops working, hopefully it will be someone else's problem by then.".
I don't think I've come across that usage. As far as I'm concerned, if it's working it aint broke, and if it is not working it's broke and required fixing. Simples! Steve
On 13/11/2009, steve-ALUG@hst.me.uk <steve-ALUG@hst.me.uk> wrote:
runlevel ten wrote:
The trouble is, there are many people in this world who use that phrase to mean "It is broke, but let's not fix it until it stops working, hopefully it will be someone else's problem by then.".
I don't think I've come across that usage. As far as I'm concerned, if it's working it aint broke, and if it is not working it's broke and required fixing. Simples!
You clearly aren't a software developer then! :) Srdjan
On 13 Nov 09:14, Srdjan Todorovic wrote:
On 13/11/2009, steve-ALUG@hst.me.uk <steve-ALUG@hst.me.uk> wrote:
runlevel ten wrote:
The trouble is, there are many people in this world who use that phrase to mean "It is broke, but let's not fix it until it stops working, hopefully it will be someone else's problem by then.".
I don't think I've come across that usage. As far as I'm concerned, if it's working it aint broke, and if it is not working it's broke and required fixing. Simples!
You clearly aren't a software developer then! :)
*If* it's functional, but potentially a nightmare to extend going forwards, it's not broken as such, just not optimal. There's a difference. (and what then usually happens is someone needs to extend it, it gets refactored and the world becomes usual again). -- Brett Parker
Srdjan Todorovic wrote:
On 13/11/2009, steve-ALUG@hst.me.uk <steve-ALUG@hst.me.uk> wrote:
I don't think I've come across that usage. As far as I'm concerned, if it's working it aint broke, and if it is not working it's broke and required fixing. Simples!
You clearly aren't a software developer then! :)
No, I'm a computer programmer! Steve
steve-ALUG@hst.me.uk wrote:
runlevel ten wrote:
The trouble is, there are many people in this world who use that phrase to mean "It is broke, but let's not fix it until it stops working, hopefully it will be someone else's problem by then.". I don't think I've come across that usage. As far as I'm concerned, if it's working it aint broke, and if it is not working it's broke and required fixing. Simples!
In my experience it's "if it ain't broke, keep fixing it until it is". -- Mark Rogers // More Solutions Ltd (Peterborough Office) // 0844 251 1450 Registered in England (0456 0902) @ 13 Clarke Rd, Milton Keynes, MK1 1LG
On Fri, Nov 13, 2009 at 9:22 AM, Mark Rogers <mark@quarella.co.uk> wrote:
In my experience it's "if it ain't broke, keep fixing it until it is".
http://xkcd.com/349/ Rick
On Fri, 13 Nov 2009 09:34:32 +0000 Ricky Bruce <rickybruce@gmail.com> allegedly wrote:
In my experience it's "if it ain't broke, keep fixing it until it is".
Wonderful And on the EMACS/vi[m] debate.... http://xkcd.com/378/ --------------------------------------------------------------------- The text file for RFC 854 contains exactly 854 lines. Do you think there is any cosmic significance in this? Douglas E Comer - Internetworking with TCP/IP Volume 1 http://www.ietf.org/rfc/rfc854.txt ---------------------------------------------------------------------
On Fri, Nov 13, 2009 at 12:38 AM, <steve-ALUG@hst.me.uk> wrote:
runlevel ten wrote:
On Tue, Nov 10, 2009 at 11:22 AM, <steve-ALUG@hst.me.uk <mailto: steve-ALUG@hst.me.uk>> wrote:
On the other hand, the adage "If it aint broke, don't fix it" is often relevant! :-) Steve
The trouble is, there are many people in this world who use that phrase to mean "It is broke, but let's not fix it until it stops working, hopefully it will be someone else's problem by then.".
I don't think I've come across that usage. As far as I'm concerned, if it's working it aint broke, and if it is not working it's broke and required fixing. Simples!
Steve
It's perfectly possible for something broken to work! Ways this can happen are many, and such things can be just hunky dory for the most common cases in the here and now. When tolerances get pushed or corner cases happen, underlying brokenness shines through - quite often to the detriment of those competent folks who have to fix it and those unfortunate users who reap the consequences. I wouldn't dispute the practical merits of moving on when something works, but the fact a bridge is standing five minutes after the engineers have left, does not prove the bridge is fit for purpose!
participants (7)
-
Brett Parker -
Marcus -
Mark Rogers -
mick -
Ricky Bruce -
Srdjan Todorovic -
steve-ALUG＠hst.me.uk