The programmers who watched Google TensorFlow Core up close and found that their daily work is: reading code and writing code; just like an excellent writer, reading good text and writing good text.
Writing good code and writing good articles are the same:
- All use one language to express / implement their ideas / creatives
- It is all mental work, long-term high-intensity writing / code writing, easy to cause cerebral infarction and sudden death
- You need to capture your own energy peak. When the energy is low, the efficiency is low, that is, students often feedback: the brain is muddy / disorganized
- If you feel tired, you must take a rest; and you must close your eyes and recuperate, you ca n’t brush your phone; you ca n’t rest by brushing your phone
- Writing code and writing articles can trigger flow , but suddenly you will find that the more you write, the cooler you are.
- Reading the code is the same as reading the article, and often encounters something that you do not understand the first time. At this time, you should calm down
, consult the information, and do the debugging until you understand. - To write a good article, read more articles; to write good code, read more code.
- The input and return curve of writing articles and writing codes is exponential . The initial input and return are not obvious. When a threshold is exceeded, it begins to explode.
