Rector fireside chat - PHPMiNDS meetup

1. A Fireside Chat about Rector

2. A Fireside Chat about
Rector

3. Programm
●
Introduction to Rector - Matthias
●
Demo time - Tomas
●
Q & A - You
●
About the book - Matthias

4. Fireside chat?
The fireside chats were a series of
evening radio addresses given by
Franklin D. Roosevelt [...] [He] spoke
with familiarity to millions of
Americans about recovery from the
Great Depression, [...]

5. Legacy code

6. Legacy code
How much pain will you put up with?!

7. At some point we’d like to
Migrate from Zend 1 to Symfony 5

8. At some point we’d like to
Go from Active Record to Data Mapper

9. At some point we’d like to
Use PHP 8 attributes instead of Doctrine
annotations

10. At some point we’d like to
Mark classes as final if they aren’t extended

11. At some point we’d like to
Introduce strict types everywhere...

12. But...
●
Too much work (development &
testing)
●
Priority is always on features
●
For now: just keep things running

13. However 1
●
Broken windows
●
Halfway migrations
●
Lack of innovation
●
(FO)MO
●
Hiring is hard

14. However 2
●
Change is scary
●
Change becomes slow

15. What would you like to do?
We’ll tell you later if Rector can do it

16. What is Rector?
●
A PHP command-line tool
●
Powered by PHPParser and
PHPStan
●
Created and maintained (mostly) by
Tomas
s

17. What is Rector?
●
Understands code
●
Improves entire code bases at once
●
Can be fine-tuned to improve what
you want
●
Can be extended by anyone for
specific needs

18. Continuous Improvement
●
Not just one time upgrades
●
Once you enable a rule it will keep
reinforcing that rule

19. CI
●
Rules can be checked during the
build
●
Rules can be applied during the
build (Rector as a team member)

20. Coaching
●
Rector can coach a team to apply
best practices
●
“Don’t forget to ...”
●
“You should do ... instead”
●
“We decided to always do ...”

21. Coaching
●
If code reviewing becomes
repetitive, automate it
●
(write a Rector rule)

23. The Future of Refactoring
●
Rector as a Composer plugin
●
Free modern standards
●
There is no legacy code...

24. The Future of Refactoring
Well...

25. Let’s switch to Tomas now

26. The Book

27. The Book
●
How Rector works
●
Its place in the ecosystem
●
Extend Rector with custom rules
●
Use TDD to safely develop those rules
●
Make Rector a contributing team
member

28. Buy it, support us
https://bit.ly/2X76GUw