Models often used by operators (3): Ability model

Pyramid principle

The pyramid principle follows four basic principles for work summary.

1. Conclusion: Express a central idea and placed in the forefront.

2, the above is unified: Each argument is summarized in the next level argument.

3, classification group: Every group is the same logical category.

4, logic progress: Each group is arranged in a certain logic order.

3W gold circle rule

Thinking mode is in the outermost layer, know what "what" you have to do, but rarely think about how to do it better.

People in the middle layer know how to "How" do better completion of tasks and goals, but rarely think about the reason for this.

Only people in the top circle are clear why "Why" do this. Why is the core nature of this matter, others are all around this center.

PDCA cycle

The meaning of the PDCA cycle is to divide quality management into four stages, namely:

P: Program (Plan) includes the determination of the principles and objectives, as well as the development of activity planning.

D: Execute (DO) to design specific action plans according to known information; then perform specific actions according to the plan.

C: Check (Check) summary results, clear results, find out the problem.

A: Processing (ACT) processes the results and problems of the inspection, and there is no solution to the next PDCA loop.

Kiss restraint

KISS is not a English word, but a scientific project replica method to promote the next activity to be better launched.

Keep (can be maintained): The reap-on activity is good, follow-up activities can continue to maintain.

Improve (requires improved): What links / factors lead to unsatisfactory activities, and it is necessary to improve in subsequent activities.

START (requires start): Which links are not implemented in this event, and follow-up need to start doing.

STOP (need to stop): Which behavior is unfavorable to the activity and needs to stop.

The KISS principle refers to the principle of simplicity in design. Summarizing the experience in the design process, most systems should be kept simplicity and simple, without incorporating unnecessary complexity, such system operation results will be optimal; therefore, the simplicity should be designed The key target is to avoid unnecessary complexity.

Data analysis six-step method

Data analysis also requires certain skills, don’t indulge in the ocean of data, data is tool, we should use tools.

1. Propose a question: What is the first question of our solution?

2. Make a hypothesis: On this issue, what is our pre-hypothesis?

3. Data Acquisition: According to this assumption, start collecting data.

4, data processing: machining the collected raw data, including cleaning, packet, retrieval, extraction, etc. of data.

5. Data analysis: After the data is finished, the data needs to be integrated and cross-analyzed.

6. The result is presented: visual data, and the specific concluding information is obtained.

SMART principle

Everyone has the experience of developing goals, it seems simple, but if it is rising to the technology level, you must learn and master the SMART principle.

The goal must be specifically (Specific) and cannot be generally available.

The goal must be measurable, which is quantified.

The goal must be achieved (ATTAINABLE), but it is not much low.

The goal must be associated with other goals (Relevant), forming ductility, and ultimately achieving higher objectives.

The target must have a clear deadline, reached within a specified time, and finally determine whether the target is achieved with the deadline.

SCQA model

The SCQA model is a "structured expression" tool, which is made in the McKinsey Consultant Barbara.

S (Situation) scenario– Introduced by the scenarios familiar with everyone.

CMPLICATION conflict– The actual situation is often conflict with our requirements.

A (ANSWER) answer– Our solution is …

Postscript: The model is just a model, the theory is just theory. These can only become tools for us to use, but they cannot be a shackle that constrains our thinking. This time the theoretical model is just the first version, and we will also increase these commonly used theoretical models, and even some theoretical models will be explained alone.

Remarks: Some images come from the network, and the data is mainly collected in Wikipedia.

Easyc ++ 41, template explicitly

Hello everyone, I am Liang Tang.

This is the 41st article of the EASYC ++ series to talk about the template explicitly.

I want to pursue a better reading experience, I can visit the Github Warehouse: EasyleetCode.

The previous article said, although the template function is very easy, there are some problems. For example, an operation is not applicable to all types, which provides a solution for this case C ++, which is a template definition for specific types. The specific specificity of the specifically here can be understood.

Let’s take a look at the example in C ++ Primer, suppose now we have a structure called Job:

For structures, it can be assigned a whole, so the previous SWAP function is the same as it.

But we now hope that when switching structures, just exchange SALARY and FLOOR two fields, keeping Name unchanged. Since we want to introduce logical changes, it is not feasible to call the SWAP function directly.

Of course we don’t have to function template, direct overload function:

Since the C ++ is specified, the priority of the non-function template is greater than the function template, so we will use this when we call the SWAP function for the Job structure.

In addition, we can provide a specific template function:

The writing of this function seems to be special. We added Template <> before the function type, and followed the <Job> after the function name. It represents this is an explicit specificization of a function template, or it is understood that the previous function template provides a Job type version. The priority of the explicit template function is higher than the ordinary template function.