[Info-vax] yet another sys$qiow question

Stephen Hoffman seaohveh at hoffmanlabs.invalid
Wed Aug 12 17:47:37 EDT 2015


On 2015-08-12 21:23:18 +0000, Jan-Erik Soderholm said:

> Den 2015-08-12 kl. 23:18, skrev kc at kayceesoftware.com:
> 
>> It's working and bosses are happy,...
> 
> That are the two things that says "do not touch anything" to me. :-)

Stopping at working code is a low-cost and low-effort strategy and 
which often works for some years, but can also be how more than a few 
projects and products end up too expensive or outclassed or even 
unmaintainable.

Technical debt tends to accumulate, unfortunately.

>> and hopefully they'll let me have time to switch to socket comm.
> 
> I might have missed something at the beginning, but why mess with it, 
> if it is working and bosses are happy?

Refactoring is generally performed to clarify code, to lower 
maintenance, to move to common code, and/or to simplify future 
extensibility.   Sometimes for performance or portability, too.

While it is certainly possible to spend too much time refactoring, it's 
also possible — or even easier — to not spend enough time cleaning up 
code, and particularly when you know and understand the code and the 
requirements — rather than revisiting the code sometime later, when you 
don't.





-- 
Pure Personal Opinion | HoffmanLabs LLC




More information about the Info-vax mailing list