As you know, MY posts are updated frequently, so I often see “productive like XX” comments in the comments section, which seems to be easier for me to write.
But in fact, at the beginning OF my writing articles also suppress for a long time, but later I gradually clear up the idea of writing articles, know what to write, how to write.
Today I put this period of time about writing the article thinking sorted out, I hope to give you some inspiration.
What to write
React, JSX, setState, Fiber, hooks, Vue, Template, reactivity, etc.
For example, JSX and Template are DSLS describing views, and setState and Reactivity are different change detection mechanisms.
If you add Webpack, there will be even more relationships.
There can be A * B combinations between any two concepts (not just technologies), which is called the Cartesian product.
When you master enough technology and think enough about the connections between technologies, there’s A * B * C *… * There are an infinite number of things to write about and there is never a problem of running out of things to write about.
So why do you feel like you have nothing to write about?
It could be that you don’t know the technology well enough, or you don’t think enough about the connections. At this time more input more thinking is good, will always find a point worth writing.
How to write
Once you know what to write, how to write it?
If I want to explain something clearly, I want to make it clear logically. That is, what concepts are involved, what are the relationships between concepts, and what is the overall process.
For example, to introduce the process of solving a technical problem, we should talk about the background, what problems there are, what concepts are involved, what technologies are used to solve them, what the process is, and what the effect is after solving them. Such an idea is logically clear.
Of course, there are a lot of logic between concepts, such as juxtaposition, inclusion, derivation and so on. These logical things seem abstract, but they are everywhere.
We often hear that writing technical articles should be structured as a total score, and that writing resumes should be structured as a Situation, Task, Action, Result, which is just a summary of some logic.
As long as you can logically clear up a complex thing, then the article is more than half successful.
How do you express it once you’ve got the logic? Code? In fact, many technical people write articles on this mistake, think that only on the code to explain the logic clearly, in fact, by reading the code to clarify the logic is a very laborious way, there are many better ways than it, such as graphic, tell a story, do an image of metaphor, etc..
It’s like the same story, which can be told in the form of a novel, a TV series, a movie, a comic book, etc.
React has many renderers, including react DOM, React Native, etc. The rendering logic is the same, but it can be rendered to different platforms.
The same logic can be said in many different ways, and it doesn’t have to be in code to make the logic clear. Many well-written articles use a combination of diagrams, stories, metaphors, and so on. Although the logic is still the same, it is much more vivid and easy to understand.
In addition, the language style will be different with the same logic aiming at different targets. For example, if the same story is told to children, it should be colloquial; if it is a formal occasion, the language should be rigorous and formal.
In addition, typesetting is also more important, through the reasonable division of paragraphs can make the logical expression more clear.
But no matter what way to describe, no matter what language style, the core of writing a good article should first clear the logic, and then express the logic clearly in various ways: the many-to-many network relationship between things, find an entrance into a tree, and then arrange the order, linear expression.
Title, cover
Title is a summary or guide to the content of the article, but also in line with the content of the article on the basis of the appropriate increase in some interesting, let the reader come in to see the idea. Do not title and content inconsistent, also known as the so-called title party, this will increase the reader’s aversion to reading the article. There will be some traffic, but the quality of the traffic will be low.
The cover is also the same, preferably related to the article, can be drawn by yourself if conditions permit, can also be generated by some tools, such as maker stickers, design, etc., can also be any picture. It doesn’t really matter.
conclusion
Any concept has many points that can be written about, and there is a combination of cartesian products between concepts, so as long as you master enough things and think about the relationship between these things enough, there will be no problem of running out of content to write about.
The core of writing technical articles is to clarify the logic, which concepts, what the relationship between concepts, what the process is, and so on. The process of expressing this logic can take many forms: diagrams, stories, metaphors, etc., not just code.
In addition, the language style should be adjusted according to the reader, typesetting, title, cover and so on should also conform to the content of the article to express.
A good technical article should be logical, easy to read and integrated.
This article sorts out my phased thinking about writing articles. In fact, I have grown up a lot during this period of time. Thank you for your support. I hope I can output more high-quality articles in the future. Let’s go for it.