Developer Ranks

Of course, the rank of a developer is a fairly abstract concept, but I will express my opinion on this issue, it is not tied to any theory, but is based only on my experience.

Junior Developer

• optimist, always underestimates the task
• constantly lacking time
• shy to show your ignorance
• constantly stepping on rakes
• hardly brings the project to the final point
• tester - enemy - for it finds bugs
• manager - not taken seriously
• not yet guided by salary, but if he is offered $ 50 more elsewhere, he may leave
• considers routine work difficult but must cope

')

Developer

• pessimist, often underestimates his strength and is afraid to miss the mark
• there is always time for a smoke break and a cup of coffee
• feel free to ask your colleagues, maybe even brazenly exploit them
• comes only on the rake hidden in the tall grass
• gritting his teeth brings the project to mind
• the tester - just zadolbal, although there is an understanding that he himself has established
• manager - why does he need my reports?
• already knows its market value, does not require an increase in salary, but learns about vacancies in other firms, and sometimes hints about its awareness
• if the tasks and the project performed are not interesting, this will have a negative impact on the project - usually the project G. shouts, the customer M ..., and what do you understand in programming

Senior Developer

• Realist, relying on his experience, sees the “bottlenecks” of the project and lays down the risks, as well as informs managers of this
• he has time to do the project, and sit at the "meetings", and also to suggest to colleagues
• can help your neighbor, feel free to say that he does not know something
• if it steps on a rake, then there are two options:
• successfully completed project - a real pleasure (both psychological and material)
• tester - adviser in terms of usability
• manager - a shield who also does not like an inadequate customer
• well knows his own worth, do not hesitate to demand an increase in salary
• understand perfectly well that the work can be routine, but it should not affect the quality of the code, it can grumble, but it will do the work

If you have enough resources, and at the same time both Juniors and Seniors are available - then the fate of the project may depend heavily on the composition of the team, so be careful:

• you should not put Junior to bison programming, if there is no person among them capable of doing his training: the beginner will not learn anything and the bison will be infuriated
• if the project is developed only by Juniors - keep abreast of the project and buy valerian - for yourself and the customer;)
• you should not put a Senior for the project “for dummies” - the project will be completed and submitted, only the developer will start thinking about working elsewhere from boredom

Well, some more information for consideration:

Errors that developers make when they start thinking about increasing the salary:

1. Overestimate yourself - demanding salary that does not correspond to your level - this is a sure way to remain without work
2. To arrange a fuss for a 10% increase in salary - often this increase can be solved without unnecessary noise and screams.
3. To find out that they are paying $ 100 more across the road, get depressed for a couple of weeks, and be on the street, because to increase the salary to a person who hasn’t done anything lately, this will be a very common mistake, never hammer to work, be professionals .
4. Considering that in a neighboring office work is 100 times more interesting.

Taki cross-post: Developer Ranks