Read about upgrades, static analysis, GPT, Symfony and Laravel

"We're looking for a Senior PHP Developer."

In 14 months old post [How to Test Monorepo in 3 Layers](/blog/2018/11/22/how-to-test-monorepo-in-3-layers/#3-after-split-testing) we talked about testing monorepo in 3 layers.

Today we'll look at the command line and run performance heavy dev tools like Rector or PHPStan on our projects.

In the previous post, we looked at [Why is First Instant Feedback Crucial to Developers?]

Do you *open-source*?

With [Symfony 5 upgrade](/blog/2019/09/09/how-we-upgraded-pehapkari-cz-from-symfony-4-to-5-in-25-days/), we need any *working* Doctrine behaviors.

In [How we Upgraded Pehapkari.cz from Symfony 4 to 5 in 25 days](/blog/2019/09/09/how-we-upgraded-pehapkari-cz-from-symfony-4-to-5-in-25-days//) post, there is a section about Doctrine Behaviors in Symfony 5.

I started to write this post as follow up for [clean and sustainable code](/blog/2019/12/16/8-steps-you-can-make-before-huge-upgrade-to-make-it-faster-cheaper-and-more-stable/) post.

"How much will cost upgrade from Symfony 3 to Symfony 4 with Rector?"

We talked about cleaning legacy code with Rector 2 months ago on 40th meetup of PHP friends in Prague.

I have a confession to make.

Are you doing code reviews?

I wrote [How we Completed Thousands of Missing @var Annotations in a Day](/blog/2019/07/29/how-we-completed-thousands-of-missing-var-annotations-in-a-day/).

Last month I was on [PHPSW meetup](https://twitter.com/akrabat/status/1181998973588037632) in Bristol UK with Rector talk.

It would take us **3 full-time months** to rewrite this code in 2017.

I'm currently working as Rector consultant for [Spaceflow](https://spaceflow.io/en), Prague-based rising startup with very nice codebase.

I wrote [Don't Ever use Symfony Listeners](/blog/2019/05/16/don-t-ever-use-listeners/) 2 months ago (if you missed it, be sure to read it to better understand this 2nd part).

School system taught me to despise old books and consider them outdated, rather about stories than knowledge.

Reporting issue is important for both you and the maintainer of the project.

I was surprised, how much of your attention got [5 Tips to Effective Work with Github Repository](/blog/2019/02/25/5-tips-to-effective-work-with-github-repository/) post.

People keep asking me about IDE plugins [for Rector](https://www.reddit.com/r/phpstorm/comments/am1qzv/update_phpdoc_comment_action/efqpv8o) and Easy Coding Standard.

Another anti-pattern that deserves more attention than it has.

Do you have 2 class with the same name?

I asked Łukasz Chruściel if we see each other on one of the conferences I'm coming with Rector and he's like: "I haven't noticed any announcements that you will talk somewhere.

Sometimes you need to achieve very simple operation - e.g. get all services of a certain type in a certain order or key name.

PHP itself is very quickly adopted.

In [Removing Static - There and Back Again](/blog/2019/04/01/removing-static-there-and-back-again/) post we tried looked at anti-patterns in legacy code from a new point of view.

Switching one framework for another is nowadays getting easier and easier.

Symfony [recently announced a new version of Twig](https://symfony.com/blog/new-in-twig-namespaced-classes) with namespaces as we know it.

The more companies I meet, the more I see `static` and `new` everywhere.

Do you prefer composition over inheritance?

We had 🍺 after PHP meetup in Prague and Tomas asked me: "We don't use Nette, but we still have many tests in Tester.

I'm happy that more and more people try to use Rector upgrade and migrate their code-bases to the ones they really want for a long time.

After few long Nette to Symfony migration series, it's time for relax.

Do you want to **migrate your project from Nette to Symfony**?

Do you want to **migrate your project from Nette to Symfony**?

A framework is just a tool.

Are you Symfony programmer?

The best programmers aren't the smartest in the field.

On the break of January/February 2019, we **migrated whole [Entrydo](https://entry.do) project from Nette to Symfony**.

Rector and static analysis help us to work with code better, but it also helps us spot new weak-points of our PHP code.

Rector had started just recently helping **instantly refactor private commercial projects**.

Following files are supported by PHPStorm and Symfony plugin for years (since 2016) and they make working with a code so elegant.

I see too many skilled developers missing `final` in every class they use.

I love to write about my packages.

It's a holiday, we want to rest and enjoy time with our families.

Do you use Symfony autodiscovery services registration everywhere and your configs have no extra lines?

This was an amazing year for me.

If there would be "Miss Deprecation of PHP 7.2", `create_function()` would definitely win.

Last week we hosted [Kirill Smelov](https://twitter.com/wbasrs) in Friends of PHP meetup in Prague.