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

I have a couple of open-source CLI apps like Rector, ECS, Class Leak, Config Transformer, Monorepo Builder and Lines, and private ones like Cleaning Checklist, Fixai, Private Rector and Entropy.

This year I've been learning Laravel and quickly adapting to most of my tools.

PHPStan and static analysis help us with detect unused private methods.

I often speak with project owners or CTOs, who ask for help with legacy project upgrades.

Discussion were always important part of my blog.

Regarding Laravel, one of the biggest "no"s in 2022 was how it handles passing services around the project.

This Tuesday, I was a guest in [2nd podcast of PHP Portugal](https://twitter.com/VotrubaT/status/1639241043248836610) folks.

This week I've been working a lot on GPT in [Testgenai.com](https://testgenai.com/).

What would you like to ride on a highway: a city bike or a Tesla car?

It's been exactly a week since I migrated this website from Symfony to Laravel.

Last week, I kicked off the first post about [tips and tricks with GPT](/blog/lets-share-fails-and-tricks-with-gpt).

Have you moved your Symfony configs from YAML to PHP with the help of [Config Transformer](/blog/2020/07/27/how-to-switch-from-yaml-xml-configs-to-php-today-with-migrify/)?

Last week, I had many interesting discussions about OpenAI and GPT on [Laracon in Porto](https://laracon.eu/).

I've been using monorepo for almost a decade, and I was thrilled with that.

I kicked off the [unit test generator](/blog/how-can-we-generate-unit-tests-part-1-testability-score) idea with the first post a week ago.

As you have noticed, apart from writing micro-packages for PHPStan, my passion is exploring the field of **generated unit tests**.

In a post from autumn, we looked at how to [develop packages in monorepo on PHP 8.1 and release a downgraded version on PHP 7.2](/blog/how-to-develop-sole-package-in-php81-and-downgrade-to-php72/).

When we come to a new code base, we look for a code quality metric that will tell us how healthy the code base is.

The PHP downgrades are a thing.

If you have not switched your [Symfony configs from YAML to PHP](/blog/2020/07/27/how-to-switch-from-yaml-xml-configs-to-php-today-with-migrify/), there no better time like present.

This bold question has been around PHP Internet for many years...

In the previous post, we set on [journey of fails](/blog/twig-smoke-rendering-journey-of-fails) with ups and downs.

In previous post, we explored [the "whys" for Twig Smoke Rendering](/blog/twig-smoke-rendering-why-do-we-even-need-it).

Two weeks ago [our upgrade team started](https://getrector.com/hire-team) to upgrade Twig 1 to 2 and Latte 2 to 3 for two clients.

Native PHP Enums came almost a year ago in PHP 8.1.

We've introduced a new way to configure PHP tools on Symfony DI.

ECS runs on Symfony container configuration to build the service model.

The beauty of [pattern refactoring](/blog/2019/04/15/pattern-refactoring/) with Rector is transforming thousands of elements at once.

We're going to visit a foreign country where living costs are just 1/3 of ours.

[Native enums](https://php.watch/versions/8.1/enums) is a new PHP 8.1 feature.

How can we create 2 tests scenarios for the Symfony Kernel project with 2 different parameters?

Working with PHPStan on level 8 is a luxury, at least for a project where you've just introduced it.

Do you have a big project where you try to raise the PHPStan level as high as possible?

You know the situation.

In the previous post, we looked at [When Symfony Http Kernel is a Too Big Hammer to Use](/blog/when-symfony-http-kernel-is-too-big-hammer-to-use).

I've been a big fan of Symfony components for ages.

Sometimes my clients need a specific CI check that spots tiny but annoying bugs, and they cannot be discovered by PHPStan, Rector, or coding standard tool.

Do you use [Easy Coding Standard](https://github.com/symplify/easy-coding-standard)?

To be honest, I have no idea what I'm doing.

Have you enabled parallel run in PHPStan and ECS?

Would you like to **understand parallel in PHP apps**?

In the previous post, we finished the conversion of [TWIG to PHP, run PHPStan on temporary PHP file and got list of found errors](/blog/stamp-4-how-to-run-phpstan-rules-on-temporary-php-file).

In the previous post, we finished the conversion of [TWIG template to clean and objective PHP](/blog/stamp-3-how-to-turn-twig-helper-functions-to-origin-object) that PHPStan can analyze.

In the previous post, we looked at [*how* to turn Messy TWIG PHP to something useful](/blog/stamp-2-how-to-turn-messy-twig-php-to-something-useful) in general.

In the previous post, we looked [at *how* to compile TWIG to raw PHP](/blog/stamp-1-how-to-compile-twig-to-php).

In the previous post, we looked [at *why* and *when* static analysis of templates matter](/blog/stamp-static-analysis-of-templates).

Today we have static analysis checking every line of our PHP code - with PHPStan, Psalm, and PHPStorm.

When it comes to merging huge pull-request, here and there, a bit of commented code slips to our codebase.

The [PHP FW Trends](/blog/sunsetting-php-framework-trends) project was introduced 2 years ago to compare download statistics over "what they say on the internet".

Would you contribute an open-source project if it would help your private one?