Is it necessary to know Bitrix to be a web developer?

Question

css

Hello. I learned some basics of html, js, css, php and started looking for a job related to web development to gain experience and so on. All the vacancies that I looked at (naturally in my city) require knowledge of Bitrix and all web studios work only with it. I tried this Bitrix myself and I’m not very good at working in it, although in the same wp I quickly began to understand what was going on.
In general, I used to think that it is necessary to know languages, frameworks and various complex techniques well, but in reality it turns out that nobody needs this. Sit down and learn the Bitrix docs (which, it seems to me, have not changed since 2010) and make a website. Tell me, maybe you should just memorize this Bitrix and become in demand? Or try to find something else?
PS To be honest, now I would like to study Bitrix as the last thing, maybe because I have little experience, and Bitrix has a high entry threshold?

Answer 1

Is it necessary to know Bitrix to be a web developer?

No, you need knowledge of technologies on which the same Bitrix is ​​​​implemented

Answer 2

There are two sides of the coin.
1. Development on the most demanded system on the market so far in the CIS ( Bitrix ). Demanded in 1 queue by customers, not developers.
You will always find yourself a job.
But you will have to put up with the current shortcomings, which are not being fixed as quickly, because. backward compatibility is supported (they cannot afford not to support it because they have too much market share). But they are still being fixed, and a considerable part of the functionality has already been rewritten for the new kernel.
2. Development on frameworks. In Russia, for example, YII, Symphony, and Laravel, which is actively gaining momentum, are common. Yii is more for small things, Symphony/Laravel is potentially for larger projects.
Working with them is more pleasant from a programming point of view, but you potentially have to write a lot of what is already written in the CMS. Although sometimes writing a new one is faster than customizing an already written one for a business task.
There is less market / vacancies on FW, + there is no stability, today one FW is popular, tomorrow another. No one has a dominant position. If you choose this branch, I would advise Laravel, it seems to me the most promising, in top studios at least the demand is growing.
The advantages of this path - you start learning programming "from the bottom", with OOP, core, no options. This is more difficult than learning CMS, there must be a good theoretical base in order not to cheat (IMHO).
Bitrix can also be studied from courses - it's easier, you first learn to understand the huge functionality from the user's point of view (learn to drive a car), and then gradually immerse yourself in writing components, modules, start studying the core (climb under the hood and begin to understand how the car generally works and internal combustion engine).
Your best documentation is the code that's under the hood, behind beautiful (or not so) interfaces. There are almost no well-documented CMS, bitrix is ​​one of the leaders in this direction.
If the skill does not yet allow you to read the source code and understand, then start the manuals).
In general, for training, monitor HH.ru on the topic: junior developer. You will be lucky if you get into a large studio with good leading specialists and a good training program. In this scenario, you will be taught to program regardless of the use of the platform and will be taught the basic practices of corporate joint development + quickly weaned from shit coding.
If you get into a small one, you will have to gnaw granite yourself, read a lot of literature, you will achieve all the same, but over a longer period. For starters, I would recommend reading:
And I advise you not to listen to populists and Bitrix haters. Many of them just worked either with the old version, or are working now, but do not learn the new kernel, do not follow the new practices, or know very little about the new kernel. And many simply spit on everything they don’t use now, in the spirit of “all fools, I’m the only smart one,” the share of constructive criticism is very small, although there is something to criticize for. If Bitrix was such complete shit as many describe, he would not have taken a dominant position in the market.

Answer 3

not necessarily, but calling yourself a "web developer" when you can't master Bitrix is ​​at least strange.

Answer 4

Bitrix is ​​a common CMS for an online store. Abroad, they have not even heard of such a thing. For example Magento. It is more flexible than Bitrix, but at the same time complex. Most likely you need knowledge of frameworks. You can write your Bitrix on them!

Answer 5

In Bitrix, not only the documentation has not changed for a long time, but the architectural approaches are outdated. Despite any technological innovations that appear in it.
IMHO, if you learn Bitrix, then you will be a person who knows Bitrix. And you will not be called a web developer. Then it will be just as difficult for you to enter normal web development as it is for a normal web developer to deal with Bitrix.
If you want to find your niche and sit down in it specifically and for a long time, then delve into Bitrix, study it, gain experience. Good and high-quality specialists in any field are quoted. But in this way you will choose the world of Bitrix for yourself and will exist in parallel with objective reality.

Answer 6

You need basic knowledge of CRM at the level of their understanding, no more. And so, it is better to develop in the software component.
And advice: forget the word "Bitrix", it hurts...

Answer 7

Dude, ask less general questions on the toaster and more code. All this discussion about CMS is as useless as it is old. I have three months of experience, I managed to work with Magento, WP, Bitrix, Joomla, Opencart and some other self-written ones. So, if you know how, you can work with everything. I still haven’t figured out which of all this is better, because in fact it turned out that I don’t even have enough knowledge of PHP, MySQL, JS and CSS. In my opinion, if you do not have a portfolio, go where they will take you. And then understand what you need. If someone is too lazy to read everything, here is a summary: At the initial stage, any CMS is just a tool in learning the language.