|
All: <snip> That is where the problem started. Imagine a shop with 20 to 30 developers. Let say 10 of them think that sub-procedure is good and make program more readable and the other think that it is cumbersome and confusing. What should the shop do? </snip> Just one thought...Standards. If the shop standard is to use fixed-format, then that is how production code is to be done. If the standard changes to use /free, then new code should be written in /free, etc. People who don't adhere to standards should be treated accordingly. If you have "20 to 30 developers" and don't have standards, that is certainly a problem unto itself! If new techniques require training, then we must also remember that it is not responsible of us to reprimand programmers (or worse) if we haven't provided appropriate training: you can't use what you don't know. Please deduct $.02 from my account. ;-) Bruce Guetzkow Information Services Director United Credit Service, Inc. Phone: 262-723-2902 Fax: 262-723-5568 Email: bruceg@xxxxxxxxxxxxxxxxxxxxxxx Web: www.unitedcreditservice.com
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
