How to Make Legacy Refactoring

Fun Again with Rector

Jan Mikes & Tomas Votruba

 

getRector.org

Hi, we're Tomas and Honza

  • friends
  • consultants
  • trainers
  • speakers
  • legacy lovers ❤️️❤️️❤️️

People: "It's not possible..."

Us: "Really? Hold our 🍺🍺!"

sli.do/rector

Code samples for refactoring to

honza@getrector.org

1. How code becomes legacy?

*2015-11

PHP 7.0 - 809 lines

PHP 7.3 - 651 lines

Symfony 4.0 - 1145 lines

1. How code becomes legacy?

2. How to get out of legacy?

Text

Text

Code becomes legacy

as soon as it's been written

Text

Text

Code becomes legacy

as soon as it's been written

Text

Knowledge

learned

Time to Refactor Legacy

1. How code becomes legacy?

2. How to get out of legacy?

3. How can we do it faster, cheaper and better?

54 357 lines

151 REST routes

90% of time spent refactoring

is precise planning

Time to Refactor Legacy

1. How code becomes legacy?

2. How to get out of legacy?

3. How can we do it faster, cheaper and better?

4. What is Rector?

= Solution to all your

PHP legacy problems

= Solution to all your

PHP legacy problems

Nikita Popov

Ondra Mirtes

Jan Tvrdik

Today is about

you!

Missing @var annotations at properties?

Good! Now you'll learn

how to use it then :)

We look for the biggest legacy PHP code.

Do you have it? Contact us ↓

 

GetRector.org

Thank you!

Rector Training in Web Summer Camp 2019

By Tomáš Votruba

Rector Training in Web Summer Camp 2019

  • 26
Loading comments...

More from Tomáš Votruba