Improve your Rector, PHPStan and CI Skills with 3 New Trainings

Do you have time to read a book now and then after work? Yes? Get Rector - The Power of Automated Refactoring and practice AST katas daily.

But not everyone has such a passion for technology and yet wants to get the work done with as few mistakes as possible. Learning a new technology alone is hard. There is too much edge-case to think about on every level of technology we use.

What if there was someone to pull you through the steep learning curve?

I believe code automation has been changing the world as we know it. From automated deploys, through coding with CI, to self-repairing systems and GitHub Co-Pilot working for you.

If you work with software, it's worth learning. Do you believe it too, but have only one spare day to spend on learning?


For you and your team, I've prepared 3 practical trainings. Each focuses on a specific area of automation that helps you automate your daily work:

1. Rector Ownage

Do you want to run Rector on your project and get the most out of it? The first steps with AST are the hardest. This training aims to fast-forward you three months of self-taught know-how in a couple of days.

2. PHPStan Guru

Do you use PHPStan every day? Would you like to learn to use more rules that would help you find bugs faster?

3. Bulletproof CI

Would you like to learn from your CI? Would you like to shorten code reviews to fraction and speed up onboarding? Do you want to avoid repeating bugs that are not part of tests?


Would you like to know more about each specific training? Check the training page.



Rector training with Quentic

Single Format

Successful and long-term automation stands on intuitive patterns. To make life easier and transparent for you, every training has:

Focused on Your Team

Why two half-days instead of 1 day? 1 day is easier to plan by the company and easier to sell to business people. It's more cost-effective for the trainer too, when it comes to attention and money.

Yet, the primary purpose of the training is to pass knowledge to your team and help your team use the knowledge in the long term. The well-rested brain learns better, and people are having more fun when the training is spread over 2 shorter days.

After the first half day, you still have the energy to try the tool at home after work. Maybe you have some questions or errors that you need to solve. Usually, you'd have to google them or ask the trainer after the training via email, waiting for a reply. That's what second half-day is for - to fill your gaps and make you grow.


Would you save time wasted on repeated boring work and make tools work for you? Let me know.

Happy coding!



Do you learn from my contents or use open-souce packages like Rector every day?
Consider supporting it on GitHub Sponsors. I'd really appreciate it!