>>>>> "TS" == Tolkin, Steve <[EMAIL PROTECTED]> writes:
TS> I am looking for the "best" and/or original wording of this programming TS> maxim: Put similarities in code and differences in data and i have also heard it the other way around, put similarities in data and differences in code. you can actually argue from either side as they both make sense in some ways. similarity could be sharing common code or using data structure to hold similar data. and code could be used to handle differences in the data and data could hold differences of each instance. so IMO the saying (in either form) is about recognizing similarities and differences and expressing them in code and/or data. this is a general analysis concept and is a fundamental skill that isn't taught enough. most newbie coders are so lost in basic syntax that they can't see how to even use a hash in ways that will reflect the design needs. this is where experience comes in too. uri -- Uri Guttman ------ [EMAIL PROTECTED] -------- http://www.stemsystems.com --Perl Consulting, Stem Development, Systems Architecture, Design and Coding- Search or Offer Perl Jobs ---------------------------- http://jobs.perl.org _______________________________________________ Boston-pm mailing list [email protected] http://mail.pm.org/mailman/listinfo/boston-pm
