1. Construct test cases and test scripts before you write your code

2. Establish clear rules for how developers will write the SQL statements in the application

Single or multiple-row queries and inserts and updates should be "hidden" behind prebuilt and thoroughly tested procedures and functions which can be optimized, tested and mantained much more effectively by a SQL guru within team than SQL statements scattered throughout each developer's codes.

3.Establish clear rules for how developers will handle exceptions in the application.

Create a single error-handling package that hides all the details of how an error log is kept, determines how exceptions are raised and propagated up through nested blocks, avoids hardcoding of application-specific exceptions