Is the programmer "too many codes and no time to think "?

For example, a friend asked me a question. I think this question also represents the confusion of Some programmers, so I may say a few words here.

We all know that at present, programmers have a high level of work intensity and pressure, and 8 hours a day is not enough. Overtime is a common practice, and almost all the time is spent on coding. So I came up with this question. If I had been coding mechanically all day, how can I think about the problem and improve it?

I think the first thing to be clear is that coding and thinking are not serial. It doesn't mean that there is no time to think about coding. Coding is to solve the problem, and find the essence of the problem and explore the solution until the problem can be solved through the Code. Isn't this in itself thinking? Not only thinking, but also profound thinking. Otherwise, you may not be competent for coding. That is to say, it looks like encoding, but in fact it never stops thinking. Quantitative changes to qualitative changes will happen in a subtle way.

Second, thinking is not an independent activity. It doesn't mean that you can't do anything when thinking. Thinking on a bus, watching TV, and thinking before going to bed ...... In addition to work, there is still a lot of time to think about a lot of things, and it is impossible to get all the time occupied by coding.

In fact, if we say "there are too many codes and no time to think", the point is not "no time". This is just an excuse. I think the focus is on escaping. It may be annoying coding. It may be a relief of stress, or it may not be able to find the direction of thinking, so I tried to find an excuse to escape it. If you have a strong desire for one thing, time will always be there. You can read technical books when others watch TV, you can write a test code to practice the design pattern when playing a game. You can get up early for 10 minutes to learn about the new technology development. Therefore, "No time to think" is just an untenable excuse. It is even more difficult to establish this excuse on the premise of "too many codes.

Here, I think we can end it. The reality is that the coding work is a little more stressful, but this is by no means an excuse for us to stop thinking and learning. "What you wake up every day is not an alarm clock, but a dream.

-- Welcome to reprint, please indicate the source of http://blog.csdn.net/caowenbin --