"Programmer's Cultivation - From Excellent to Excellent" Reading Notes (1) - Time and Quality Management

Time management:

1. Like a hoarder, I misunderstood the real reason for hoarding unfinished work. When hoarders have to throw away something, they think it's a storage problem. It's as if I say I'm time-poor because there are only 24 hours in a day. (do it quickly and discard the little things, don't let the tasks accumulate)

 

2. Everyone needs only one item on their To-Do (task) list, and the others are superfluous. (According to the author's later statement, in fact, only 1-3 to-do items need to be arranged every day)

 

3. Tools are like floating clouds, but your brain and heart will accompany you all your life. Learn to trust them. ...if one thing is really important, you remember to do it. If you forget it, maybe one day you will remember it. If you haven't remembered it, that's fine too! (The United States is a highly developed country in the IT industry, and Jeff himself loves his career very much. "The Analects of Confucius" has a cloud: I think Jeff may have reached such a state when he is seventy years old. For limited people, it is still necessary to use tools to manage)

 

4. I think it pays to persuade management to support something like an idea day or a 20% time policy, no matter where you work, because the success stories that come with it are numerous and obvious to all (according to the famous 8020 rule, he Saying that "usually 80% of a company's profits come from 20% of its projects", then how to use fragmented and leisure time is indeed an interesting topic)

 

5. If your work environment always feels like a critical moment, then you must solve the problem first (important things are not solved, and will often fall into a state of emergency. This may be caused by your own work environment, and also It may be caused by some unknowing habits)

 

6. Creative problem-solving requires "daydreaming" (though effort is important, genius still needs that 1% of inspiration)



 

Quality Management:

1. Usability testing is the most effective way to do this: make small changes in a two-week cycle, and quickly discard the bad parts (small and fast iterations are agile's outstanding characteristics)

 

2. Most developers don't test at all! The real value of unit testing is that it forces you to stop and think about testing. (Ensure that developers think outside the development thinking and stand in the perspective of testing)



 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

The above is excerpted from the book "The Cultivation of Highly Effective Programmers", in parentheses is the blogger's own understanding

Guess you like

Origin http://43.154.161.224:23101/article/api/json?id=326476841&siteId=291194637