Ramping Up on an Inherited Project - From Review to First Steps

Details

Work in this busy industry long enough and you're bound to be given stewardship of an important code base with no documentation and no surviving development team. How do you get started? Where are the common gotchas? How do you fight the urge to write it off as aging, legacy code and push for a rebuild?

This month at the GPUG I'll be walking through how I ramp up on an inherited code base. It's going to be a wild ride!

Also, this month we'll be raffling off a licence to PHPStorm (or any other JetBrains IDE)!!!