How not to get into the "wrong" PHP?

Question

PHP

Good afternoon. At the moment I work as an administrator, but I want to move into development. I chose PHP as the language, but I consider it a slightly dangerous choice for the following reason. As far as I know, there are 2 incarnations of this language
1) Riveting sites and IM on WP, Bitrix and other things. It is clear that programming is primarily a job and a profession, but IMHO I want to be engaged in the normal development of complex projects in the future, with a normal architecture, code quality, a normal modern process with CI / CD, etc.
2) Actually "normal" PHP development with modern frameworks and everything that is described above.
Question: how to distinguish a company where you should respond, where from the start you can comprehend and improve your skills at a professional level and not get into the IM riveting offices? The question arose for the reason that I recently saw vacancies where the requirements in my inexperienced head became, if not mutually exclusive paragraphs, then at least they looked strange to me. On the one hand, the requirements included knowledge of stylish-fashionable-youthful Redis, Symfony, understanding of Git-Flow, Agile, etc. and there are also indicated - knowledge of WP 1C-Bitrix. How can this be understood? Like something that will have to be occupied with various planned tasks? If you highlight the essence of the issue - how to distinguish a company in which it will be possible to grow into a PHP developer, and not a web master.

Answer 1

normal architecture, code quality, normal modern process with CI/CD, etc.

No one is safe from a shit project, regardless of php, java, c#, js, brainfuck ...
Most often, architecture, code quality, and this is all developed where it is critical for business and business understands, either we write normally, or ass . But these, unfortunately, are few. You can ask at the social security how much downtime is allowed and how often they occur. If the late time per minute needs to be coordinated a week or more in advance, most likely they care about the quality. If downtime in half an hour is not really a problem - all of us *at))

On the one hand, the requirements included knowledge of stylish-fashionable-youthful Redis, Symfony, understanding of Git-Flow, Agile, etc. and there are also indicated - knowledge of WP 1C-Bitrix. How can this be understood?

This is the incompetence of the person who made the vacancy, nothing more.

Like something that will have to be occupied with various planned tasks?

Ask a recruiter a question

If you highlight the essence of the issue - how to distinguish a company in which it will be possible to grow into a PHP developer, and not a web master.

Ask a few questions:
0. Are you a food company?
1. What is legacy from their point of view, what is its percentage in the project and how often is the technical debt returned?
2. What is the development process from start to finish?
3. What standards and requirements are used?
4. What is the test coverage?

Answer 2

Interview and trial period not only for the applicant, but also for the company. You need to be able to ask the right questions, and if you lied, then this is determined on a trial period

Answer 3

PHP is still a language for writing homepages. If the project succeeds, people continue to suffer. So it goes. Another thing is that most projects on the web do not need all this.

Answer 4

I have been working with Bitrix of the year 4. On the current project, both kitty and dry and solid and composer and unit tests and microservices and putterns. I saw a couple of projects on frameworks, the hands would be cut off by "normal php people". The main thing, as mentioned above, is that the company should be a product company with its own development team. Layout, front and back separately. Most web studios need a human archaeologist. This is useful at first, for the outlook, but over time it is better to choose a specialization. I can do something on the front both on react and vib and do it sometimes, for a change. But the back is closer, by no means can I call myself a full stack.

Answer 5

if you work as an administrator, can you look towards dev-ops?

Answer 6

how to distinguish a company where you should respond, where from the start you can comprehend and improve your skills at a professional level and not get into IM riveting offices?

• Product company
  
• Project on modern framework (Symfony/Laravel)
  
• Write auto tests
  
• Do code reviews
  
• CI / CD is configured (i.e. if someone made a shitty pull request, because of which the tests fell, it simply won’t be possible to merge it)
  
• Deadlines don't expire. Practice shows that it is impossible to make a good quality project in constantly burning deadlines.
  
• There is a team. From the points above, this is already clear, but just in case, I will write separately. Do not go to a company where you have to work alone, or in a company with another single programmer.
  

Well, you need to be mentally prepared on the first working day, if you see a bunch of shit code - just get up and leave.

On the one hand, the requirements included knowledge of stylish-fashionable-youthful Redis, Symfony, understanding of Git-Flow, Agile, etc. and there are also indicated - knowledge of WP 1C-Bitrix. How can this be understood?

This means that the company has both good and bad projects. Guess who will deal with the bad ones.

Answer 7

Well, you yourself answered your own question where vp and Bitrix are shit, where the last php and the last laravel chocolate