Bang Writing articles/code

[1] "write a paper must be quick, first of all to get out of the draft, no tube rotten to what extent."

This sentence I really have experience, Bo Master from childhood to university to graduate students, writing composition can level has been very food, seldom experience what the idea of the fountain, flowing feeling, ideas are easy to stall, attention is also easy to disperse. Writing code is a lot of the time, but the main reason to write code is because you can't remember many APIs. I hope I can improve the speed and efficiency of my writing (or writing code) by blogging a little bit.

Write an article/code

· Come on, no matter how bad.

Many times we will look forward to the "perfect" expression, so tangled in the local expressions, but often fall into a lot of detail problems leading to the speed of writing forward greatly reduced, many times the loss of the candle, to upgrade some of the details may not be insignificant, but paid to not quickly see the overall cost.

· Picture, and then put it up.

Do not be afraid to forget, believe that you can finally see the picture is not done. If the idea is often interrupted, the efficiency will be low, and most importantly, it is sometimes impossible to tell whether many details are really necessary to spend a lot of time before there is a clear understanding of the whole.

· Unknown API or step, and finally put it up

First, the whole part is to write the basic idea of the article or code, not to say that the local is not important, local and the whole is inseparable. However, if you frequently interrupt the overall idea of writing, attention is easily dispersed, and it is easy to fall into the details and forget some important steps.

· Key point List

The goal of writing a list of key points in an article or on a draft paper is to have a rough idea of what you want to write, and if you quickly complete the prototype to get a clear understanding of the whole, then the list of keys can make it easier for you to get a sense of the whole, so that the article or code will be built more smoothly. The main thing is to reduce some important points in the process of writing your own articles.

· Review multiple times

The first draft must be flawed, especially the fast-building first draft (which can also be code), the need to review the code for errors, whether there is a poorly considered place, add missing details, delete redundant details. Because it is the first draft I have just written, it will be easier to review, the process of review can deepen the understanding of the article.

Read the article/code

· Try to figure out every noun/api.

This is the basis for accurate assurance, although they do take a lot of time, but the local and the whole is inseparable, many of the key details are not clear and can not understand the whole. We have a tradeoff between detail and a quick understanding of the whole.

· Question List

Sometimes it's not clear how many problems you have now, and as time goes by, it becomes clearer. Sometimes you can not dwell on the current problem, but you should make a record.

[1]http://blog.sciencenet.cn/blog-202041-400825.html

Bang Writing articles/code