On 2/17/11 10:03 AM, John Harvey wrote:
> I think he's referring to the "hype" factor.

Sort of.

Rewriting code instead of building upon existing code would be sort of like 
tearing 
down a building and building it again, from scratch, because it needed a new 
paint 
job or heating system.

Sure, programs, like buildings, do reach the end of their service life and it 
no 
longer makes sense to keep putting another layer on top of the ancient 
technology. 
But then you'd have a brand-new 1.0 program, not version 7.0 of the old program.

Yes Stephen, I refactor and rewrite methods quite often, but only when it makes 
sense 
vis-a-vis the current change or enhancement I'm implementing. My code isn't 
static 
but constantly evolving. This isn't what I'm referring to with the phrase 
"major 
rewrite".

Paul

_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: 
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.

Reply via email to