I read the article “Ten Principles of Improvement for Engineers” written by Meituan technical team and got a lot of feelings. The ideas mentioned in the article are not only helpful for novice drivers, but also for experienced drivers. Summarize the important descriptions and write them down in the hope that you can keep encouraging yourself.
Original text: juejin. Cn/post / 684490…
Abstract:
Principle 1: Owner awareness
- Conscientiousness is the bottom line of work. Take responsibility for the results delivered.
- Being proactive is a higher level of Owner awareness. Do your job well and take the initiative to do your “job” as well. Drive the progress of the team to ensure the smooth progress of the project. Don’t put limits on yourself and strive to become a better person.
Principle two: time concept
- Work should be organized. The plan is granular enough to be reviewable at key points in time.
- Prioritize your work. It is divided into four quadrants according to importance and urgency.
Rule 3: Start with the end
- Think clearly about your goal and work hard to achieve it. Set goals based on the problem and then optimize. Do requirements while focusing on goals and benefits and use effectiveness. Solving specific problems is the goal of technical optimization.
- Learn with purpose. Purposeful learning is better than fragmented reading.
Principle four: Closed-loop thinking
- Communication should have a conclusion, notice TO have feedback, TO DO TO have acceptance.
- Take the initiative to give feedback periodically. Whether the project is progressing normally and whether any problems need assistance.
Rule five: Be in awe
- Learn the team’s existing practices as soon as possible and stay in tune with the team.
- If there is something wrong with the specification, the whole group can discuss it and update it in time.
Rule six: Nothing is more than two
- All reviews and questions should be discussed no more than twice. In this way, the stakeholders are forced to do as much as possible to meet the needs and design plans. Prior to the review, an attempt is made to reach agreement with all interested parties and there will be discussion.
- You can’t make the same mistake twice. Make a recheck after each failure, analyze the cause of the failure and define the executable TODO LIST.
Principle 7: Design first
- Focus on early architectural design.
- Write designs that others can understand. Good design must be logically clear and easy to understand, and the details can be implemented.
Principle eight: P(output)/PC(capacity) balance
- The system needs to continuously optimize its architecture while supporting business requirements. Blindly do requirements without optimizing the system, the system is getting worse and worse, and ultimately affect the business; Conversely, a system with no business output will eventually die.
- In the process of doing projects, we should continue to improve our technical ability and soft quality through learning and summarizing, and apply them to project implementation and delivery to achieve a win-win situation.
Rule 9: Be good at asking questions
- First, ask questions. The best ideas and decisions can be made only in debates.
- Know how to ask questions. You need knowledge, expertise, experience, and critical thinking.
Rule 10: Empty cup mentality
- Examine and reflect on yourself all the time. Confidence must not degenerate into complacency.
I feel that it is not easy to remember, so I should summarize it again (similar to software design thinking) and try to be brief and easy to remember.
Clear goals (start with the end) -> Design first -> Business technology complement each other (P/PC balance) -> Plan and prioritize (sense of time) -> Work carefully and take initiative (Owner consciousness) -> Abide by and improve specifications (maintain awe) -> Think more and ask questions frequently (good at asking questions) -> Timely feedback, acceptance (closed-loop thinking) -> do not make the same mistake (only two things) -> empty cup mentality