The saddest thing in the current situation is that IT is gradually becoming an industry where there is no word “stop” at all in the number of responsibilities per person.
When reading vacancies, sometimes you even see not 2-3 people, but a whole company in one person, everyone is in a hurry, technical debt is growing, the old legacy looks like perfection against the background of new products, because it at least has a dock and comments in the code, new products are written at the speed of light, but as a result, they cannot be used for another year after they are written, and often this year does not bring profit, moreover, the cost of the cloud is higher than the sales of the service. Investors' money goes to the maintenance of a service that is not yet working, but which has already been released to the network as a worker.
As an example: a well-known company whose remaster of an old game received the lowest ratings in the history of the industry. I was one of those who bought this product, but even now this product works terribly, and in theory should not have been released in this form yet. Refunds, rating drop, a huge number of user bans on the forums for complaints about the work of services. The number of patches does not delight, but terrifies, but still - the product is not usable. If this approach leads to such results for a company that has been developing since 91, then for companies that are just starting out, the situation is even worse.
But we looked at the results of this approach on the part of the user of the service, and now let's look at the problems that employees have.
I often hear the statement that there should be no DevOps teams, that this is a methodology, etc., but the trouble is, for some reason companies have stopped looking for noks, dba, infructors and build engineers - now it's all a DevOps engineer in a single person. Of course, in individual companies there are still such vacancies, but they are less and less. Many called this development, I personally see degradation in this, it is impossible to maintain a good level of knowledge in all areas, and at the same time manage to work no more than 8 hours. Naturally, these are fantasies. In reality, many IT workers are forced to work both 12 and 14 hours, of which 8 are paid. And often without days off, because “I was given a task, there are no docks or curves, and the service costs money”, and for 1 in the cloud, you can, in principle, not get a salary in a couple of months, especially if you work on an IP basis. We are in fact losing the word in business, along with the separation of duties, I am increasingly faced with the fact that managers get into development processes without understanding anything at all, they confuse business data and application operation, as a result, chaos begins.
When chaos begins, business wants to find the culprit, and here you need a universal culprit, it is difficult to pin the blame on 10+ people, so managers unite their positions, because the more duties 1 specialist has, the easier it is to prove his negligence. And in the conditions of Agile, finding the “guilty” and spanking is the basis of this methodology for doing business in management. Agile has long been out of IT, and its main concept has become the requirement of daily results. The problem is that a highly specialized specialist will not always have a daily result, which means it will be more difficult to report, and this is another reason why businesses want “specialists in everything”. But the main reason, of course, is the payroll - he is the main reason for all the changes, for the sake of the allowance, people agreed to work for themselves and that guy. But in the end, as in other areas, it has now simply become an obligation, for a smaller payment for a larger number of services provided.
Now you can often even see articles that developers should already be able to deploy, should deal with the infrastructure next to a DevOps engineer, but what does this lead to? That's right - to a drop in the quality of services, to a drop in the quality of developers. Literally 2 days ago, I explained to the developer that you can write and read from different hosts, and they proved to me with foam at the mouth that they had never seen anything like this, here it is in the settings orm host, port, db, user, password and that's it .... But the developer knows how to launch deployments, write yamls .... But he already forgets about unit tests and comments in the code.
As a result, we see the following - constant processing, searching for solutions to problems outside of working hours, constant training on weekends, and not to increase income, but to keep ourselves afloat. Developers are forced to help a DevOps engineer with CI / CD, and if the developer does not have time, he starts to shut up, and managers start to compost brains, and if this does not help increase the desire to work overtime, then apply penalties and fines, the person is looking for a new job, leaving behind a technical debt the size of Everest, as a result, the debt begins to grow among developers as well. they are forced to write code with less refactoring in order to have time to help either an old or a new DevOps engineer, and managers are quite happy with everything, because there is a guilty person and he can be seen right away, which means that the main rule in Agile management is observed, the guilty one is found, the results of his flogging visible.
Once at ITGM I made a presentation “when we learn to say no” - its results were very revealing. A huge number of people believe that this word is taboo, and until we stop thinking so, the problems will only grow.
Partially inspired me to write this article., but I will perhaps write it in less pleasant terms later.
Only registered users can participate in the survey. , you are welcome.
Have you encountered at work when the employer tried to replace several people with you?
-
65,6%Yes, I run into it regularly
-
5,4%Yes, encountered 1 time15
-
15,4%Didn't notice43
-
13,6%I'm a workaholic, I work overtime myself38
279 users voted. 34 users abstained.
Source: habr.com