How to write code in Laravel if one of the two programmers is a symphonist?

Question

Laravel

I'm very good at improving the architecture, however, I remember the main postulate "the code should be easy to read for any developer who got a job in the company."
A good programmer came to the team and he writes in Symfony-style in the Laravel project, since he had not worked with Laravel before, but only worked in Symfony.
As a result, its code is very different from the code of the previously written project - new folders, each method in separate files (commands) and raw database queries bypassing Eloquent.

In this case, how to properly build coding standards and how to organize it? After all, before, even any front-end developer or temporarily connected to the project can immediately join the project without additional excursions and add their modules in the syntax familiar to the project, but now there is a problem with reading its code and when it is not changed and bugs are detected, you have to comment on its code and write your own so that the work of the site does not stop.

and it is clear that in symphony the level of abstraction is much more deeply nested, but the project is on Laravel

The solution is this for now: First, discuss all new developments that differ from the usual Laravel-Style within the team, then create a regulation in the form of a description of folders, files, their assignment, links to the documentation, where this is explained, and only after that, when everyone has read and given the go-ahead to implement their innovations in the project.

Answer 1

In laravel you need to write in laravel. Or don't use laravel. if an employee writes in the style of a symphony or plays the piano virtuoso, let him do what he can and in the place where it is appropriate. it is strange to try to adapt the team to the employee, and not vice versa.

Answer 2

For a long time, the first thing to do in Laravel after installation was to create a Models folder. This already contradicts what has been said.
You can even assume that the person is talking "on a symphony", most likely this is whining that laravel is shit and should be done in its own way. First of all, you need to answer the question. Can one person do better than a huge community? Laravel offers freedom. If you don't want to use something, turn it off and don't use it. This is a framework for its intended purpose, it speeds up work on routine tasks. If a person is good but not ready to change his beliefs, another good person is needed. Otherwise, one person will simply shit on the project to everyone else, and then sit and figure it out and what to do with it.