Session Abstract: |
Most PL/SQL is written but not designed. Too many packages are almost random accretions of procedures and functions, which makes them hard to use and maintain. Yet following a handful of simple design principles drawn from architecture, town planning, and product design could dramatically improve the clarity and utility of our PL/SQL APIs. This presentation shows how patterns from those disciplines can be applied in PL/SQL programming at both the schema and procedure levels. |