Maintainability is super important! I don't want to be the only
person supporting every bit of code I write :)
Also if you expect someone else to use your code. Good documentation
is the way to go. Which is also why I write tests first. Then make
them stop failing.
On Sun, Dec 7, 2008 at 10:24 AM, Friedrich Gurtler <fgurtler@gmail.com> wrote:
> On Sun, Dec 7, 2008 at 3:25 AM, Ron Johnson <ron.l.johnson@cox.net> wrote:
>>>
>>> You can argue resource management all day long. However I take those
>>> things into consideration. Most of my programs have very limited
>>> client side footprints. I know throwing more hardware at a
>>> performance issue is barbaric. But I have not had to go there yet.
>>> We have SO MUCH head room on our infrastructure for our current
>>> customer base... I can't see a reason to spend time making it more
>>> efficient when I could spend time adding useful (to humans) code
>>> instead.
>>
>> I *could* read that as "the hardware's so powerful, who gives a rat's arse
>> about the quality of the source code".
>>
>> But I'm sure that's not what you meant... Is it?
>
> I read that as "my goal is to provide value" which is what I want to hear
> from a developer.
>
> Also, you seem to equate "quality of the source code" with efficiency
> first. I tend to equate quality of the source code with correctness,
> maintainability, some other stuff, then efficiency.
>
> -- Fritz
>
___________________
Nolug mailing list
nolug@nolug.org
Received on 12/07/08
This archive was generated by hypermail 2.2.0 : 12/19/08 EST