Lots of Drupal projects get into trouble from time to time and many Drupal businesses need to take over existing codebases. How do you perform an audit on a project and determine what to keep and what to throw away?

What are the automated forensic tools you can use to find the pain points in a Drupal application? And once you find those pain points what is the criteria you should use to determine the best course of action?

Who is this for? Any developer who has inherited an existing Drupal codebase.

In this session we'll cover:

• Drupal modules you can use as a starting point for project audits
• The PHP tools you can use to discover the scary dark corners of a Drupal project
• Test rigs for seeing how and where a Drupal application will break
• Practical approaches to development triage; when to use band aids versus when to operated on the patient.