Reducing headaches when inheriting someone else's technical debt

hcderaad

Having your own business means you can run your development processes the way you and your clients want. Nice! You have full control, you can set up every detail to your own level of quality and comfort. Except that every once in a while you'll be asked to take over an existing project or a client will introduce legacy components into your shiny, fully agile processes. And let's just say that these usually don't come accompanied with extensive volumes of documentation and they might already have a history of being passed on from developer to developer multiple times.

 

Your clients expect you to be able to jump right in, “Because it's Drupal, right? You know Drupal. How hard can it be?”

 

This presentation will help you develop a systematic approach to dealing with these issues:

 

  • How to scan a legacy project for areas of complexity and possible problems.

  • Tools and skills to identify weaknesses in applications early on

  • Hints on developing a strategy also when having to refactor parts of a legacy system

Register NOW

Session Track

Coding and Development

Experience Level

Intermediate

Drupal Version