Assume it isn't correct. Is it fixable?

My general approach in any software context is to give maintainability at least as much importance as functional accuracy. In some cases, I'd go so far as to say that maintainability is more important than correctness!

It's easier to fix a maintainable but bugged program than it is to do anything with an accidently obfuscated program that happens to to work for last week's requirements, but not this week's.

All common sense caveats apply.

Comment on Assume it isn't correct. Is it fixable?

Replies are listed 'Best First'.
Re: Assume it isn't correct. Is it fixable? by GrandFather (Saint) on Jul 31, 2008 at 21:00 UTC
which is why items 2 - 6 address that issue. ;) Perl reduces RSI - it saves typing	[reply]
Re**2: Assume it isn't correct. Is it fixable? by wol (Hermit) on Aug 01, 2008 at 14:04 UTC
I'd read the numbered points as an ordered list, implying that point one is the number one priority. Maybe I'm thinking too hard today, but read that way it's perfectly comprehensible, and ceratinly useful for reminding people that there's more to consider than whether anyone has complained about the results (yet). And I'd agree with each point in the list. However, I thought I'd contribute the slightly contentious view that sometimes accuracy is not the number one priority. Of course, if everyone agrees with that, then it's not so contentious. Bah - don't tell me I'm back in the mainstream again.	[reply]