This document outlines 10 ways to intentionally wreck a database, including using a single spreadsheet instead of normalization, random naming conventions, no keys, no foreign keys, no constraints, non-atomic fields, magic numbers, polymorphic fields, entity-attribute-value modeling, and letting an ORM take care of database design. It also provides information about upcoming PostgreSQL conferences and how to contact the author.