Best Practice Exercise

Esteemed colleagues,

I have the opportunity to develop an entirely new set of "best practices" and methods concerning the development standards in my shop.

Some things to think about might be...

O Naming conventions
O Service program structure
O UDFs
O Shared SQL cursors (courtesy of release 7.1)
O Triggers, Constraints, etc.

Everything but the database (which is "legacy") is on the table for a re-vamp. However, to some extent, the database is open concerning new tables, indices, etc.

I am leaning toward service programs that will contain common procedures...but what would be your preference if you had this opportunity?

RPG will be the development language. This is to tap into our already very strong rpg-devloper base. SQL will be the IO language of choice. We do not currently use commitment control, but intend to.

I have a blank sheet! If it were yours, how would you fill it out?

I'm not trying to get you guys to do my work, but it seems a shame to ignore such an experienced (opinionated) group!

Dream big!

Steve Needles

==============================================================================
This communication, including attachments, is confidential, may be subject to legal privileges, and is intended for the sole use of the addressee. Any use, duplication, disclosure or dissemination of this communication, other than by the addressee, is prohibited. If you have received this communication in error, please notify the sender immediately and delete or destroy this communication and all copies.