Re: Opinions please : You can't (shouldn't) fix Stupid, remove the Stupid first and then see if you still have a problem.

On Thu, Oct 28, 2010 at 2:25 PM, Johnathan Meehan
<johnathan.meehan-Teh1U3IPPOKF51e+ZNOf3QC/[email protected]> wrote:
> Hi John / All,
>
> The best thing about code that doesn't exist is that it's guaranteed
> 100% bug-free. :)
>
> To my own opinion, I tend to be a little more cautious even when I'm
> sure I'm sure. I stick to one thing at a time, make a note of problems I
> see whilst fixing the current and get back to them later. My real
> concern, especially against a large code base, is missing a connection
> and actually making my life harder with multiple bugs on the go (read,
> burnt very subtly but very badly before).

Yeah. A lot of the time those nasty tangled-up messes are there for a
variety of reasons. Cumulative bug fixes and work-arounds for nasty
issues.

It doesn't sound like it's the case here, but...it's nice to know how
the Stupid got in there in the first place.

-- James