Sounds like a real pisser <g>.

>Rip;
>
>There are at least three approaches to standards as applied to programming. None, some and well done! One thing about standards – if everyone within an organization uses the same standard the political gods will be pleased. If the standards are well thought out that is even better as there is less chance of something biting you down the road. No standards is a means of failure, and a poorly conceived standard is not much better.
>
>While working for the “pre eminent” Urine Analysis Company for less than one hour, I was given the task to solve a serious problem. A consultant had written a program that decided to stop working and it was the main billing and chemical analysis program for the company. Result – no billing for the month and many records had invalid data (law suite time). Invalid data could mean people going to jail, which is serious business.
>
>After looking at the code I found the following naming convention. All parameters and variables had the following prefix: pp_ - not bad for a urine analysis company you say? Well, I found the problems, solved them and told our director about this “convention”. The director thought it was very unprofessional – however, it may have been just a programmers sense of humor at a company that had no standards.
>
>Tom