What can a real senior/lead developer besides knowing some language and its frameworks?

Question

IT education

What is worth learning for the first courses in order to increase your "price" as a developer in the future? What can a real senior/lead developer besides knowing some language and its frameworks?

Answer 1

What can a real senior/lead developer besides knowing some language and its frameworks?

Whatever you study, you will graduate as a junior. They become seniors not by learning the syntax of 10 programming languages, but by doing 10 major projects. How and on what they are made is not so important, the main thing is the lessons that the developer learned from them.

What is worth learning for the first courses in order to increase your "price" as a developer in the future?

Based on the above: study "some language and its frameworks" at a high level, so that immediately when you get a job, you will start to benefit and gain experience in implementing projects, and not fighting with the java compiler. Learn your IDE, use it effectively. Well, look at related areas to broaden your horizons: graphic design, UX, other programming paradigms.

Answer 2

After graduating from a university, an erroneous opinion arises of possessing the necessary knowledge, and even the question arises, what else?
And also - everything!!! All that narrow-minded teachers who are outdated for a century or two could not tell you. The problem is that a team leader earns like a whole department of teachers, so the best ones become team leaders, and the worst ones teach you how to become a junior, so that later you can either become a teacher or start reading a lot, work a lot, think a lot and either die or become a team leader.

Answer 3

The main difference between senior/lead and middle and junior is that a senior is able to do a task without asking technical questions.
He himself is able to understand the system and do what needs to be done quickly and efficiently.
You will never hear from a senior that it is "difficult" or "impossible" - he just sits down and does it.
All this is called "professionalism" - and it is he who is the main feature of the seigneur. And those frames and languages ​​that he uses are just tools.

Answer 4

has experience
how do you know about hangs in curl without having experience with it in a highload project?
instead of highload in curl everything is fine
, bare knowledge is not enough

Answer 5

I've been in programming for over 20 years (from junior to senior, team lead, etc) and still sometimes I get the impression that somewhere I'm still a junior.
Languages ​​must be studied. Frameworks are a waste of time

Answer 6

In addition, the lead must be able to coordinate the development team. Without an experienced lead, the project will stand still or be developed extremely slowly and inefficiently.

Answer 7

He knows how to understand the requirements of the customer (sometimes even better than the customer himself), find solutions to meet them, make the most optimal use of the resources available to him. The customer here is not a specific client, but an adjacent non-technical unit that set the task. They don’t teach this at the institute, they don’t write it in books, after 4 years quality work will come by itself.

Answer 8

Communications.

Answer 9

He should be able to develop a COMPETENT APPLICATION ARCHITECTURE, based on:
1. His experience (from previous projects)
2. Functional requirements of the Customer.
And, if necessary, create such an APP from start to finish without outside help.

Answer 10

You need a variety of combat experience on dozens of projects, which you will earn only in the course of practice. Everything else is instruments and decorations. It doesn't matter what. It is important that it works and does not fall.
Considering that business is a living thing, the signor should be able to build an architecture in such a way that flexibly and dynamically change anything to anything else in the course of the play, and everything continues to work. It is very desirable to do all this quickly and efficiently, while exploring and mastering new things on the fly.
In fact, you have to really learn new things all the time. It doesn’t happen that you have mastered some kind of stack and are overgrown with moss, and you have everything in a bunch for 20 years.
In general, the main thing here is an assertive desire to solve a hundred new and unknown problems every day in the normal mode, as usual.