Xie Everest provides a source of inspiration. Thanks to Master Huo for coding all the scenes. Please find him if you can't write well.
Tucao HR
Let's continue to discuss how to set the KPI of technicians.
Ali Technology has an article "How to Quantitatively Evaluate the KPI of Technicians", written by Zhang Jianfei. He believes that the KPI of technicians can be decomposed into "three contributions": business contribution, technical contribution and team contribution:
1. Business contribution: including demand control, business projects and business innovation.
2. Technical contribution: including design reconstruction, technical impact, code review, innovation and efficiency improvement, and code quality.
3. Team contribution: including recruitment, new talent training and team atmosphere.
The second "technical contribution" was dismantled, and the author described it with some cases in his work:
1, application quality:
Responsible or * * * jointly responsible for the application quality score (can be investigated from the dimensions of code repetition rate, circle complexity, layering rationality, etc. ) and what the technicians have done to improve the application quality score.
2. Design reconstruction:
In the customer communication project, technicians have modeled and designed the CRM sales field, which is abstract and reasonable;
It is found that the classification of packages in infrastructure is unreasonable, and it is redesigned and reconstructed.
It is found that the error code in the current system is confusing, and a new error code specification is formulated and the code reconstruction is completed.
3. Technical impact:
Team sharing strategy model has been well received by students.
Accepted the invitation and shared the SOFA architecture at the industry conference.
4, code review:
When reviewing the code, I found that there may be hidden dangers of thread insecurity.
When reviewing the code, I found that there was an unreasonable design. Using the responsibility chain here can solve the problem gracefully and has certain expansibility.
5, innovation and efficiency:
It is found that it is a waste of time to start Pandora Boot in local test, so writing test container greatly improves the efficiency of self-test.
It is found that some sample codes don't need to be written, and optimistic locking and pagination are just to simplify the annotation of codes.
At a certain project or technical point, a patent is produced: business configuration based on domain model.
6, code quality:
The number of bugs and online faults after testing (the system can extract them without filling them in).
The unit test of a module has been perfected, and the problems have been found by automatic regression for many times.
Next, I will share with you a set of diagrams of hooks. The writer is a technical KPI made by Bigger (Big Data Engineer).
Bigger believes that although technicians prefer a free environment, for the entrepreneurial team, if everyone does not follow the norms, then the technical team of this company is a mess.
What KPI should technicians use?
Based on the comments on Ali's technical articles, the author clearly believes that:
KPI is active, and it should be emphasized in different stages.
1. At the start-up stage, KPI should be inclined to the business as much as possible. When survival is a problem, talking about technological ideals is simply utopia.
2. When the income is gradually stable, we should try our best to tilt towards technology. Only in this way can we talk about stability. When the whole system is on the right track and the system is robust enough, it will be more appropriate to keep the ratio of 6/4 (business/technology). Of course, this should be flexibly regulated according to the actual situation of each enterprise.
This also puts forward a multi-dimensional assessment standard for TL's own business, technology and market. Pure technology or pure business is not desirable. After all, everyone is waiting for commercial organizations, and commercial profit is the first. Everything else should be centered on this, and technology optimization also serves commercial profits.
Therefore, talking about business without technology, or talking about business without technology, is a utopian thinking.