Make Yourself Slow and Relax

My sleep is not good, long-standing.

Over the last one months, iterative development has been tense and busy. A neurotic person like me has a sense of being out of the real world, thinking about the problems they encounter without time and place. Too immersed in one thing, easy to forget a lot of other things, the brain's capacity seems so small, it is not as good as a computer's memory, has not been upgraded. Instead, it will gradually age.

Code written and deleted, deleted and written, Jane and Jane, re-construct the re-construction. I am a natural love for the pursuit of perfection, the code as a work, a variety of fine research methods are used. In this way, others can understand, they can understand, the problem is less, the cost of maintenance will not be large. Of course, the precondition is that you have to do the coding work very well, leaving yourself sufficient time to code, test, refactoring, business functions to keep combing, function code to keep clean up. A lot of complex business logic, either you don't comb it out or you don't realize it gracefully.

Different and the previous development process, I in this time tried to use the imperfect TDD method, the overall effect is good. The so-called imperfect, that I did not fully apply the TDD process; on the contrary, in the early stage of development I still run small steps, quickly set up a basic function of the framework, so that the fundamental ability to work. Next, each scene use case overwrites, writing use cases, verifying the correctness of the function. In the process of scene verification, we can find the blank or blind spot of the previous analysis, complement the scene, write the use case, and so on.

In addition, read your code over and over again. Read your code in a skeptical manner, at least three times, and ask yourself:

• Can I read it?

• Logic, right?

• Do you realize complexity?

• Can you just be a little simpler?

• Can anyone read it?

• Good maintenance?

For each line of code, write test cases to overwrite. First of all to believe in computers, and then to dare to challenge themselves, again to do it quickly. Practice is the only way to verify truth.

I think that future development work can continue to use this method of work. The advantage of this is that the test case is used to drive the development function, using test case to ensure that the existing code function is correct; The code compensates for the scenarios and use cases, and the use cases validate the functionality. Of course, this requires your manager to leave you plenty of time to do these things.

Ah, found that wrote, and back to the old bank. It was to be said that the reason for slowing down, off the topic. Fortunately, this half hour I slowed down, the brain slowed down, the body relaxed. Slow down, relax, and you'll have a better idea.

I am not a computer, I need time to organize myself, more need time to reflect on myself.

I'm not a computer, and I don't want to keep idling like it does. I need time to stop and look back on my tracks.

Let me slow down, let me relax, I will have a better state.

Make Yourself Slow and Relax