|
|
Posted by Jerry Stuckle on 08/25/07 00:30
Sanders Kaufman wrote:
> ELINTPimp wrote:
>
>>
>> Refactoring your code doesn't always mean you screwed up in the design
>> or within the actual logic of the code. Most of the time, it has to
>> deal with improving your code to meet new business requirements.
>
> I understand all that... and how "refactor" doesn't necessarily mean
> that everything's a mess.
>
> In fact, I just "refactored" some code in which I was passing CSV
> strings, but needed to change that to an array.
>
> But I just told my payer that I did something fundamentally wrong, and
> had to fix it before I went on. Had I said I need to "refactor" my code
> , it wouldn't have been clear to her what happened. Worse, I think it
> would have scared her into thinking that I was another one of many
> coders she's hired before who bend over backwards to avoid admitting
> that they made a mistake... while charging her for it.
>
> I realize that in some circles, that kind of biz-speak is acceptable -
> but those aren't my circles.
>
But that's not refactoring. You changed the interface. Refactoring
does not change the interface - just the internal workings.
--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================
Navigation:
[Reply to this message]
|