Forced profanation - “market” management
Sometimes in IT companies or IT departments, among project managers, an opinion begins to appear that a developer after 25 years is not the same (author’s comment - “he cannot quickly ... but write slowly and carefully”), and a programmer after 30 - a strange social phenomenon, an overgrowth (note of the author - "very intelligent, finding fault with the requirements").
Managers are increasingly beginning to maliciously misunderstand why a PHP developer, such as an experienced one, spends so much time on ... securing a piece of a web page, and struggling to perform javascript "in all popular browsers" fights two days, wasting money on the company ".
Achtung! Management companies from the “market” have leaked into your company, who have no idea what effective work with the creative intelligentsia is, and they continue to sell potatoes out of the habit and bring cheap dildos to you and the management.
')
Then it will only get worse, you can not lose time and it's time to prepare for a coup.
ProductOwner from the market:
We are familiar with the path of a typical Programmer, remember it ...
The beginning of the way
Some, especially gifted individuals, begin to write code in high school, some are involved in development projects in their student years. But the most active phase of the acquisition and application of knowledge in practice begins after graduation.
First projects and teams
For the first time, developers encounter large systems and, in practice, comprehend why they need to leave comments in the code, observe modularity, write automated tests. Large projects are actively re-evaluating academic knowledge, especially in the field of object-oriented programming.
Important is the experience gained in the course of working in a team of programmers. It is necessary to get used to the fact that there are more experienced and clever colleagues, there are beginners, there are untidy ones - you need to suppress disgust for someone else's, especially poor-quality code - and this is not easy.
It takes a lot of time to master the comfortable tactics of working with command tools (trackers, version control systems). And the tools in different teams are different, you have to relearn.
First libraries
I noticed that there are few developers capable of creating high-quality libraries. One out of ten, maybe less. I think due to the fact that it requires an understanding of the REASONS of the emergence of modularity, the concepts of OOP and the internal, and not the "syntactic" comprehension of patterns. If you managed to confuse in the past and fill it up with a couple of projects - experience will come in handy. And if you sat on the support / revision of the ... year code, even better.
Understanding relational theory ... in practice
Here the specialist will not interfere with design experience and then support projects with intensive use of databases. I was surprised to find that people seem to be able to program, but they cannot explain the solution of the problem in terms of relational algebra :-) We need practice and reading books — thick but interesting. More time.
Broadening horizons
Sometimes there are developers learning at the same time competing technology - to better understand the core. Met such pairs: java - c #, java - php. Really useful practice.
Narrow specialization
And technologies tend to thrive. Take javascript. Not only is the language “special” in itself (one model of prototype inheritance and closures is worth it), it is also a dog that works differently in different browsers. And in order to professionally solve tasks on it - IMHO must be hung daily on specialized forums, study the differences, read articles - in general, keep yourself in shape. The situation is similar with other popular technologies.
Back to basics
And if you are intensely drawn to the "basics", whence everything went - Unix, C and system programming, then it will definitely take the next couple of years of evenings :-)
In general, the older you are, the deeper you dig, you specialize, you begin to understand the concepts of the OOP from within, you already agree with several programming patterns, perfect your skills and see what else you can learn.
Ops, the developer is already 30, and to whom, and under 40 years. And there is so much more interesting ahead!
Plans for the future - narrow specialization, expertise
Experts understand that the way to managers is fraught with rapid loss of skills and the acquisition of fighting knowledge of survival in analog systems - countering trolling, intrigue, envy and other spiritual and moral feces, far from slender matmodels, OOP and design patterns :-).
Therefore, it is better to continue pumping and growing in the direction of an expert with narrow qualifications. Developing experts can actually earn at a little slightly lower than top managers in certain types of companies. Not bad and without dirt.
Ideal Specialist Working Day
You come to understand that you need to view technological news every day, at least an hour, to be aware of events. It is also a good idea to use another hour for immersion "in depth" - repeat the types of joins, explore the subtleties of MySQL replication, understand and test the keys of the top command ;-)
Whack - forced profanation
Yeah, we got to the topic of the article. The stupid management from the market refuses to understand how a programmer, sitting at the console for the last 10 years, cannot deal with the subtleties of the Oracle database in the evening, if he has optimized queries from the MySQL database last week? Or why a programmer working on PHP for the last 5 years and creating excellent libraries is horrified when he tries to create javascript code that is portable between browsers.
People do not understand what makes the Specialist engage in PROFANATION, working on the technology that is little known to him, taking sin on his soul :-)
What to do?
IMHO, this often happens in our domestic companies and this is due to illiterate management, managing high-tech specialists.
Managers need to be taught in courses, how to manage IT, damn it, and not to recruit people from the street and put them on the head of professionals - “you know how to scream and you know how to enter the browser, then you will be our project manager.”
The case may take an even more sad turn. “Cheap” management from the market, feeling its professional unsuitability, poorly developed brain (in contrast to the brains of specialists) with strong ambitions and a sense of the illusion of power - begins to simply hate developers and troll madly.
What to do. Fight these werewolf-managers. Expose them to fools on PlanningPoker and functional demonstrations. Connect adequate IT companies: tehdir, hands. development - it is not too late to build an open and formal business process in which the dullness and inexperience of project / product management will be visible to company management.
At least the processes will become less emotional, predictable, more independent of market phrases “I need a website launch in a week,” “I will fire you,” “I will find a student for five hundred bucks that works faster.”
If nothing happens, do not lose hope and try to find a company in which you want to work for many years, improving your skills and giving yourself to her.
All developers sincerely wish good luck and energy in self-realization.
Managers are increasingly beginning to maliciously misunderstand why a PHP developer, such as an experienced one, spends so much time on ... securing a piece of a web page, and struggling to perform javascript "in all popular browsers" fights two days, wasting money on the company ".
Achtung! Management companies from the “market” have leaked into your company, who have no idea what effective work with the creative intelligentsia is, and they continue to sell potatoes out of the habit and bring cheap dildos to you and the management.
')
Then it will only get worse, you can not lose time and it's time to prepare for a coup.
ProductOwner from the market:
We are familiar with the path of a typical Programmer, remember it ...
The beginning of the way
Some, especially gifted individuals, begin to write code in high school, some are involved in development projects in their student years. But the most active phase of the acquisition and application of knowledge in practice begins after graduation.
First projects and teams
For the first time, developers encounter large systems and, in practice, comprehend why they need to leave comments in the code, observe modularity, write automated tests. Large projects are actively re-evaluating academic knowledge, especially in the field of object-oriented programming.
Important is the experience gained in the course of working in a team of programmers. It is necessary to get used to the fact that there are more experienced and clever colleagues, there are beginners, there are untidy ones - you need to suppress disgust for someone else's, especially poor-quality code - and this is not easy.
It takes a lot of time to master the comfortable tactics of working with command tools (trackers, version control systems). And the tools in different teams are different, you have to relearn.
First libraries
I noticed that there are few developers capable of creating high-quality libraries. One out of ten, maybe less. I think due to the fact that it requires an understanding of the REASONS of the emergence of modularity, the concepts of OOP and the internal, and not the "syntactic" comprehension of patterns. If you managed to confuse in the past and fill it up with a couple of projects - experience will come in handy. And if you sat on the support / revision of the ... year code, even better.
Understanding relational theory ... in practice
Here the specialist will not interfere with design experience and then support projects with intensive use of databases. I was surprised to find that people seem to be able to program, but they cannot explain the solution of the problem in terms of relational algebra :-) We need practice and reading books — thick but interesting. More time.
Broadening horizons
Sometimes there are developers learning at the same time competing technology - to better understand the core. Met such pairs: java - c #, java - php. Really useful practice.
Narrow specialization
And technologies tend to thrive. Take javascript. Not only is the language “special” in itself (one model of prototype inheritance and closures is worth it), it is also a dog that works differently in different browsers. And in order to professionally solve tasks on it - IMHO must be hung daily on specialized forums, study the differences, read articles - in general, keep yourself in shape. The situation is similar with other popular technologies.
Back to basics
And if you are intensely drawn to the "basics", whence everything went - Unix, C and system programming, then it will definitely take the next couple of years of evenings :-)
In general, the older you are, the deeper you dig, you specialize, you begin to understand the concepts of the OOP from within, you already agree with several programming patterns, perfect your skills and see what else you can learn.
Ops, the developer is already 30, and to whom, and under 40 years. And there is so much more interesting ahead!
Plans for the future - narrow specialization, expertise
Experts understand that the way to managers is fraught with rapid loss of skills and the acquisition of fighting knowledge of survival in analog systems - countering trolling, intrigue, envy and other spiritual and moral feces, far from slender matmodels, OOP and design patterns :-).
Therefore, it is better to continue pumping and growing in the direction of an expert with narrow qualifications. Developing experts can actually earn at a little slightly lower than top managers in certain types of companies. Not bad and without dirt.
Ideal Specialist Working Day
You come to understand that you need to view technological news every day, at least an hour, to be aware of events. It is also a good idea to use another hour for immersion "in depth" - repeat the types of joins, explore the subtleties of MySQL replication, understand and test the keys of the top command ;-)
Whack - forced profanation
Yeah, we got to the topic of the article. The stupid management from the market refuses to understand how a programmer, sitting at the console for the last 10 years, cannot deal with the subtleties of the Oracle database in the evening, if he has optimized queries from the MySQL database last week? Or why a programmer working on PHP for the last 5 years and creating excellent libraries is horrified when he tries to create javascript code that is portable between browsers.
People do not understand what makes the Specialist engage in PROFANATION, working on the technology that is little known to him, taking sin on his soul :-)
What to do?
IMHO, this often happens in our domestic companies and this is due to illiterate management, managing high-tech specialists.
Managers need to be taught in courses, how to manage IT, damn it, and not to recruit people from the street and put them on the head of professionals - “you know how to scream and you know how to enter the browser, then you will be our project manager.”
The case may take an even more sad turn. “Cheap” management from the market, feeling its professional unsuitability, poorly developed brain (in contrast to the brains of specialists) with strong ambitions and a sense of the illusion of power - begins to simply hate developers and troll madly.
What to do. Fight these werewolf-managers. Expose them to fools on PlanningPoker and functional demonstrations. Connect adequate IT companies: tehdir, hands. development - it is not too late to build an open and formal business process in which the dullness and inexperience of project / product management will be visible to company management.
At least the processes will become less emotional, predictable, more independent of market phrases “I need a website launch in a week,” “I will fire you,” “I will find a student for five hundred bucks that works faster.”
If nothing happens, do not lose hope and try to find a company in which you want to work for many years, improving your skills and giving yourself to her.
All developers sincerely wish good luck and energy in self-realization.
Source: https://habr.com/ru/post/285406/
All Articles