|
Hi, it is for sure not the first time, that anyone encounters such environments, born and maintained in times long ago and where decisions have been avoided since long. However, under my point of view, where I have had to deal with similar situations, there two points to put standards in place: 1. Elaborate these standards 2. Apply them to any new programme etc. 3. Any change which is to take place necessarily will have those standards now implicit. 4. Establish a timeframe and budget to change/replace structure wise the remaining items one by one. 5. Clean up your own house 6. Implement a change management system After you have started, you should try to to enthuse other people from those different countries to offer them a return benefit in change of co-operation. By experience, they will accept that, even you may encounter there still people not willinng to co-operate. If you then can extend your plan and activities, you are on the right way, hard but with success. Have a good day, Joachim Aschauer SAP development Support, Walldorf(Germany) -----Original Message----- From: Peter.Colpaert@honda-eu.com [mailto:Peter.Colpaert@honda-eu.com] Sent: Dienstag, 26. Juni 2001 09:38 To: RPG400-L@midrange.com Subject: RE: Standards and Egos (was RE: ILE Propaganda) Trivial decisions... I've heard of them, but that was a long time ago. I have tried implementing a 'standard' in the environment where I work now, but that's nearly impossible, since the application is used in 10 different countries, each with their own local modifications. Moreover, the application itself (if you can call it an application, I like to refer to it as the junkyard) consists of RPG II programs in S36 procedures (yuck), RPG 3 programs with cycle logic, internally described files, level breaks and all that nice stuff, RPG/400 programs with externally described everything (except printer files of course, who needs external printer files?) and even some ILE-esque programs written with an RPG 4 skeleton nobody understands since the programmer who pronounced it 'the new standard' was fired. Even something as trivial as whether or not the Enter key is used to proceed to the next screen is not the same in every program. So how do they expect us to use standards in such an environment? Just my two Euro-cents. Peter Colpaert Analyst-Programmer Honda Europe NV Langerbruggestraat 104 B-9000 Gent (Belgium) Peter.Colpaert@honda-eu.com ---------- A computer scientist is someone who, when told to 'Go to Hell', sees the 'go to', rather than the destination, as harmful. ---------- "Bartell, Aaron L. (TC)" <ALBartell@taylorcorp.com> on 25/06/2001 22:21:27 Please respond to RPG400-L@midrange.com To: "'RPG400-L@midrange.com'" <RPG400-L@midrange.com> cc: (bcc: Peter Colpaert/HE/EU/HONDA) Subject: RE: Standards and Egos (was RE: ILE Propaganda) But even trivial decisions can save a ton of time in the end and can be considered a tool. If I code completely different than what everybody else is used to and then they have to come and modify my program, they are going to have a heck of a lot of time to put into that program. Especially if they are used to all of the indicators being different and naming conventions are different. Aaron Bartell +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +--- +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.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.