The maximum level of incompetence of a web developer

Question

Career in IT

The question arose, what is it like to still remain a developer? When “saturation” occurs and for further career growth and / or welfare growth, it is necessary to master areas that are not directly related to development, such as people management (set tasks for others and monitor the implementation above all), economics (making certain decisions from the point of view of economic feasibility , taking into account, say, the resources available to the project - the simplest case, sort of), analysis of the subject area and business processes, and so on, which is very different from "write code, bl .., tests and draw class diagrams."

The question arose in connection with the preparation for interviews and the frequent question there “where do you see yourself in N years?”, But how is it, what do I see (received the TOR, sat down, fulfilled it, well, clarified, if something was not clear, discussed options with colleagues, offered the authorities a choice of several with an analysis of the technical pros and cons, etc.) is called plainly and I don’t know. What is the “maximum” position, working in which it is necessary to solve only technical issues, not to manage anyone, not to interact with anyone except superiors and immediate colleagues (“parent” and “brothers” in the hierarchy), etc.?

Or the only option is the eternal Junior/Middle, and for development to change jobs, technologies, tasks, starting almost from scratch each time?

Answer 1

@asci , wow, just black or white?
Do you, I suppose, classify yourself as a "misanthrope"? (well, it is unlikely that a person would call himself a "chatterbox").

He is a good specialist, owns a thousand technologies and tricks, patterns, etc. however, she does not like working with people.

It is very doubtful that one can know every technology (thousands of them!) and at the same time know the details of each. Know a little about a lot or a lot about a little?
Secondly, the position of a team leader, and even more so an architect, implies responsibility for the team, its results and composition (including selection to the team). And not only in the form of a formal Lego constructor according to those. skills, but also psychological (human) compliance with the team.
From those whom you call "talkers" (well, at least Product/Project Manager -> Team-Lead/Architect -> CTO/CEO) depends on the conditions in which the team will work. If the PM is sensible as a technical manager and, lo and behold (without irony), is also at the “middle” level, most likely you will work without dibility “arrival at 7-30, fines, table meter by meter, the customer wants here and there is a little thing, and also a hat, a second monitor? / air conditioning? - why??".
Maybe you are lucky and you have not met the above described on your way and take the surroundings for granted.
@VolCh , on your question, I think that starting from the team lead, you will already have to think about related industries and the best ways to achieve the company's goals.

Answer 2

The developer, as a rule, develops faster than the company. To keep up with yourself, you will most likely have to change jobs, in the modern world this has already become the norm in some way. You don’t have to start from scratch - you still have experience in your head, deep knowledge of the craft and developments, for which your clients (employers) are willing to pay more and more each time. And to employers who ask the question “where do you see yourself in N years” instead of “how to organize the independence of the modules of this system,” I would be wary. There is a risk of falling into a sect with a corporate shiz (I worked for one for some time), it will take years of your life, and in return it will give you a stable salary, KPI and corporate parties with the “mafia”.

Answer 3

> What is the "maximum" position, working on which only technical issues need to be resolved
Obviously, the position of the developer. But in general, one must understand that there are limits to what one person can do, since his productivity is limited. Therefore, in order to solve more complex problems and further growth, it is necessary to organize work in such a way as to delegate some parts of the task to others.

Answer 4

I think, since the reason for the questions at the interviews, then the answer should be appropriate. Such questions are asked not to find out the real state of things, but to test the hypothetical purposefulness of a person. Moreover, the company itself, when asked how it sees itself in 5 years, will not answer anything real and will say standard “castles in the clouds”. So give her what they want - lie too! Say that you want to be the chief architect, technical director, and you will encroach on the position of CEO.
Yes, and do not forget to ask later how the company sees itself in the same 5-10 years (oh, how many in our industry), and what they can give you.

Answer 5

at the interview they study your readiness and desire to work in this
company