preface
Because there are many business lines, an intermediate developer is in charge of every project in the company. So there is some training and guidance. The following content is all from a personal perspective to give some reference.
Technical ability
Basic daily development requirements. Front-end technology system.
Ability to quickly acquire and learn new technologies
Every head is likely to face a system need to use other new technologies, or no contact with technical before, need to charge here have their own learning methods and learning ability, can in a short period of time to master a foreign technology, fast into the development, and in the process of development continue to accumulate and improve the new technology
Guide and assist junior students in solving problems
This link can not be missing, here requires comprehensive technology and ideological guidance. When helping junior students to solve problems, it is not only to solve problems for them, but also to carry out technical communication and solutions between the two sides. It’s a promotion for everyone.
- Improve the technical comprehensiveness, communication and problem solving skills of the person in charge
- Improve the elementary students’ knowledge and understand other people’s thinking about this problem
Planning ability
Planning ability depends on whether the person in charge has a clear plan for the work.
Technical system planning
Selection of consideration
- Whether the service requirements can be met
- How easy it is for the current team to mature the technology stack
- The current technology system is matched with the relevant technology system
- Go and play and see for yourself
Output of relevant technical documents
When researching new technology, form the habit of technical document output, you can record some pits or use methods
Human Resource planning
Manpower gradient planning
According to the volume and complexity of the project, a specific number of high school juniors should be planned.
- Complexity determines the number of high – and middle-level students
- Size determines the primary number
Manpower quantity arrangement
There must be repetitive labor movements, specific quantitative arrangements for this part.
Task division planning
- The difficulty of the task is divided among different developers
- Reusability considerations
- Task Schedule
The first two determine the specific time division.
Risk planning
- Task completion
- Degree of task completion
There are two types of risk: how much the task is accomplished, and how well the task is accomplished.
Development is completeandTask to completeIt’s two different things.
Emergency response ability
It doesn’t normally happen, but in human conditions, it can happen. With existing resources, solve relative problems.
Business ability
In fact, students in front of the business ability for various reasons, generally do not understand more than the back-end.
Sorting out business processes
Use swimlane diagrams or flow charts to sort out business processes
The representation of business key fields and data on our systems
After sorting out key fields and data based on the business logic process, the significance of some key data is known when the interconnection interface is used.
Participate effectively in business reviews and consider the combination of business and technical implementation
Business review should not be regarded as a cut scene, which requires your own thinking and combing. Others’ explanations are always others’. If you do not understand them, you cannot understand whether there is a problem in the business implementation in the development process. Additional training on how to participate in the business review will follow.
Cooperation ability
Collaboration is divided into two parts. One is the project team and the other is the department team.
And the project team
The development dimension
There’s a couple of sections here that we’ll have a session later on where we’ll talk about it.
- Product review
- The back-end alignment
- Delivery test acceptance
Front end small team
- Task allocation
- Task check
- Task risk
Reasonable distribution, timely check, anticipate risk
The management dimension
- The project manager communicates the progress of the task
- Report risks & and response
- Weekly work reflected
conclusion
- Report to: Project Manager
- Report content: progress and wind direction
- Reporting method: weekly report
And the department team
Because in our company, the front-end department is a dashed line. We may be in different project teams step by step, but the front-end still needs to do unified improvement and information sharing from the overall technical direction.
- Unified technology stack
- Configured development collaboration
- Information sharing, plug-in or business component precipitation, and other project cost savings
Front-end instrumentalized development:Bitsun-inc.yuque.com/vghmle/yuf2…
Components to precipitate
Business precipitation
Ability to communicate
Communication skills can reflect a person’s way of thinking and whether they have their own way of expression.
expression
The way of expression determines whether the communication is effective or not. Sometimes we may communicate for a long time but still not talk about one thing. When talking about any problem, don’t directly talk about the problem, clear the context synchronization, and then communicate. Sometimes, when I talk about some problems, I don’t have the key points for a long time, and I just feel confused because I haven’t sorted out the problems well, so I just come up with them directly. Everything: there will be input – – process – – – output. Then we will input and output clearly, which process is wrong, directly to the context of the cause and effect of their own clear, and then clearly expressed.
Focus of the object
- Project manager, leader report work: focus on schedule and risk, details need not be stressed.
- Department personnel: It is mainly about sharing information, and human resource risk.
- Team members: communication with internal team members is to synchronize the big direction, and the details must not be spared. Because the focus is on the implementation of the technology.
Input and output
We communicate with different people with different inputs and different outputs.
- Output refers to what we want to achieve.
- Input refers to the information we need to send to each other.
judgment
Judgment depends on whether a person has overall control of the project. Judgment ability lies in having the confidence to judge and make decisions on matters in the project.
Ability to frame
Framework capabilities determine whether a person can handle the non-business logic of a project.
Ability to analyze and solve problems
This one thing is extremely important, it is a person’s comprehensive ability to reflect.
Technical breadth, depth, logical analysis ability [part of structural thinking] reflects.
Architecture ability
Mental ability
As for mental ability, IT is not put together with the above, but it is also mentioned, because some students in the team have reflected some mental activities with me before.
Scenario: Maybe we have everything planned when we plan the mission, but the final result is delayed. There could be a number of reasons. The team members worked overtime for no reason, the joint adjustment was not well completed, the early technical scheme was not well realized, or there were problems. And then I feel like I can’t. There is a cognitive denial of the self.
We can’t decide everything, and things don’t always work out the way we think they will. The only thing we can do is to do what we need to do well, and if the results may be off, let’s just keep trying. We don’t have to have bad feelings about ourselves.
Do what you know, and know what you know.
Therefore, we pay more attention to doing our own thing, and we have our own way to deal with the emotions we encounter.