Answer the question
In order to leave comments, you need to log in
How to make a development plan for a strong developer?
I have strong developers in my team, much stronger than me. How to compose Ypres for them? If they seem to know almost everything in their stack, but we don't need a new one?
Answer the question
In order to leave comments, you need to log in
We all walk different paths, and usually, if you look ahead, you always see different paths.
Usually, it's enough that you look ahead and try to follow all the paths that you can see. A new technology has appeared that solves not a new problem - and not one path has opened up, but many, because in addition to development, there is also, in particular, the problem of integrating new solutions and devops, which I advise everyone to dive into.
By and large, there are two roads: the samurai road and the shogun road.
A samurai has no goal and only a path. This path can lead deep into the technology, to the origins of its design, to the features of its device. But the path can be winding. Also, this path can lead to related issues, where the technology has a slightly different embodiment. There are always several ways and tools to solve one problem, let the samurai follow the path to study them all. Write in the Node.js + Typescript stack, but there was no case when it was necessary to optimize the bottlenecks in C ++ - and here's another untrodden path for you. But it would be fashionable for Rust as well. And in C. Or replace a whole module with a bottleneck that was rewritten to Net core. Maybe also replace part of the front with Blazor? What problems can arise in the process?
If a samurai doesn't look ahead, he will soon go blind and think he "knows everything". But do not confuse the illusion of having knowledge with the number of kilometers traveled. Whatever the number, the journey is not over yet and never will be.
To walk the path of the shogun, you need to reject the boundaries of the familiar world of the samurai and find a goal. This goal should be a reincarnation into a new existence. The one following the path of the shogun must go up the mountain until the sun rises, and with each new peak a perspective and hundreds of paths will open up, but the shogun will not walk on them. His way is that the shogun sees the perspective, from a height he can see the other side of the horizon and the whole pattern of paths. He can see how the paths, like rivers, merge into roads, many of which lead to cliffs and dead ends. The path of the shogun should lead him to meaning. Perhaps this is the opening of a commercial enterprise, or it is (F)OSS, or the position of a shogun-team leader, or a manager who has the goal of becoming part of the leadership of the current company.
How can a samurai be helped to follow one of these paths? No, this should be done by the samurai himself. All that is required from a well-wisher is to indicate the direction and approximate duration of the specified path. Samurai himself chooses which road and which way to go now.
Why should someone make this plan for them, and even why do they need it at all?
If there are strong developers in the team, then just try to go to the gym regularly. Find out the training program. Do not be afraid to use steroid drugs (they will help to avoid various injuries).
In general, it’s interesting how the conditional middle will teach a senior and make a plan for him, but you can take a roadmap as a basis, well, there’s a typical one like this https://github.com/kamranahmedse/developer-roadmap , it’s googled like this roadmap senior <sphere>
The plan for a strong developer is an excuse for not being able to pay him a salary corresponding to his knowledge and experience.
The plan for development is necessary for business.
Developers need technical business tasks and WORTHY! salary.
How exactly and with what tools they will solve problems is not a business task.
The development time and cost of creating, operating and maintaining what will be created is HERE! MAIN indicators for business in the technical part. Everything else is done by people who understand this better.
Business - controls the profit.
Developers - control the tool that makes a profit.
well, if they are such cool guys, they probably have their own vision of where and how to develop - just discuss with them their plan, their wishes and formalize it as required by the company.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question