A little insight (2) Understanding Amazon culture and talking to Teacher Zhang

In recent work, I have learned a lot, and sum up.

As a former Amazon employee, the leader shared Amazon's core values ​​and had a deep understanding.
[1] Dive Deep.
[2] Don't make the same mistake twice.
[3] Everything speaks with facts.
[4] You should know the details of the things you are in charge of, and you should not know one or the other.

I believe that many people have not done a good job in these aspects. When encountering new tasks, you must first think about whether there are loopholes in the process you designed, and whether there is a more perfect way.

Case (from self):
A project I was responsible for had a detail because the data was provided by a lower-level project. I was not very clear about this detail at the beginning. After the leader asked me, I repeatedly asked the responsible colleague several times before I became clear.
This means that the details are unclear. Although the project is not responsible for providing data, you should also understand how the underlying data is constructed.
If you ask once, you should try to clarify all the details, instead of asking if you are still unclear, strive for efficient communication and not waste everyone's time.
If you suspect that other people's projects or data are wrong, you must speak with data. If there is no data, first find the responsible test to confirm whether there is really a problem with the process.

Think:
Have you practiced these points? Knowing is easy.

I was fortunate to listen to a lecture on <The Art of Code> by Mr. Zhang Miao from Baidu.
"Many programmers focus on how to implement the code perfectly, but do not thoroughly sort out the business and underlying data."
"Many people have typed code for ten years using object-oriented languages, or process-oriented thinking, when the task comes , you should not worry about the realization of the process first, but think about the data first, understand the data, and clear the boundaries between objects before you start."
You can follow the public account "Teacher Zhang Says", which has PPT and video addresses.

think:
Is it because when the task comes, you rush to realize it but find that it is not what the product wants?
Is it still process-oriented thinking Java friends?

Amazon Core Values: http://www.qiyewenhua.net/Article/2013/47621.shtml