Breaking in to ILE

I totally agree with Eric DeLong, and he explained it excellently.

And be sure to use long names for your objects and methods. When done
correctly, your code should read like regular english, and it is quite
natural to have some prefix or identifier that is application specific,
since some methods can be similar, but intone different processes. Long
names may take more time to write, but since we end up reading a line of
code 10 times more often than changing it, you will appreciate the
clarity of long names.

You would not want to confuse something like
Vendor_GetMailingAddressForBilling() and
Customer_GetMailingAddressForBilling() and
Vendor_GetShippingAddressForReturns( )

- John Voris

When you're done, you wind up with a series of nouns (business

objects) and verbs (procedures) that you use to build your business
applications.

Adr_GetLocation( lCustomerID : 'SHIPTO' : CustShipTo );
If Adr_IsValid( CustShipTo );