How to write a good tech blog
During the process of work, I found that for a lot of things are sciolistic, is not very clear, in the end is very easy to be fuzzy. Technoledge blog if you have a good summary is a better way.
Why blogging ?
Firstly even if frogetten you could go back to look at, still be able to recover from your thinking.
Secondly,to summarize, also find some potential problems;
Thirdly, blogging is advantages to your communication technology. Many large companies have their own internal technology bolg platfoem, write your own technology blog , for a technical personnel, I would have some sense of achievement.
In the process of accessing to information on the internet, often can see some technology blogs or nonsense, or typography disorder, or code accounts for 60% of the space, and some even is wrong, can let a person produce musunderstanding. So,it's better to summarize here what should be a good technology blog, as well as structured their bad habits. This blog is personal idea, is a fundamental thing. Avoiding by all means detailed accordingly.
How blogging?
1, write a blog with clear purpose,list your goal
Often see this blog, which blog for blogging. Such as an introduction to the use of the socket interface method of blog, list a bunch of code, gather together in a few words: "first... second... finally..." , even if it is OK. If your purpose is to "practice how to use blogging software", or "list interface", even "method" to practice writing, you may reach the goal. But I want to write a technology blog, the first is to clear the purpose of the blog, usually learn a technology, a technical problem of what, such as "learn Linux memory management mechanism", "to solve the kernel pannic problem", "pass the time."
Not all things are to write a blog to record, what should have their own judgment value of writing, something worth writing.
— list your problem or goal ahead
2, Write own blog
Posted reprinted a lot of each other on the net, a good blog often reproduced, I suggest that donot easily reproduced on other people's posts and should write my own blog.As a same knowledge point, or a same question,the understading of others is likely different. If easily reproduced after reading other's blogs, it means that you lose a opportunity to experience or self learning. Maybe someone would say"the same architecture diagram of GFS, I painted also is such, so also he painted, this is because the GFS hierachical principle is like that." Here are not asking any details yourself to do so, but to have their own thought, your own understanding, such as what is the principle of GFS stratified out ? if i'd like to do, how would to do so?
— Add your thought necessarily
When reprinted?
Write your own blog is not means the idea that not to reprint others, for example, I have read a blog, and after experiment, find it's exactly the same as that blog, not too much or too less, if you want to write your ownself, then there no need to spent time writing it again. In addition, as well purely records of blog, you can also reprinted, such as C language operator priority, and of course, repeoduced or the original is not important.
In addition, reprinted other people's good blog as your own original,not only no tasty but self-dulusion.
show respected to author
If in the blog reference other people's blog, can be referred to in the resources, if they are completely reproduced, also should give the source.
3,the blog is a summary, not a process
Bloging is a process of problem solving sometimes, in order to solve a problem, today have adopted A method, but found it's not work,tomorrow adopted B method also found it's not work, then adopt C method the day after tomorrow, and fount it is working, then the blog should start writing after C method.
When I start write blog, I often appear this kind of circumstance: since a technical not clear, i want to learn about, and then open a technology blog, check information and fill in the blog, the result is basically a process about read, copy, paste, read, copy, paste... Finally gained knowledge is empty. When In the chagrin of my own cache why so little, at the same time, I also consider whether that is a right way?
Then I thought, if you want to master a technology, knowledge, probably need to such a process:problems in practice, theoretical study problem, practice to solve the problem, theory summary. I think under many of circumstance I was missing three parts of these things, only the process of "theoretical study problem".
Later, I wrote the blog is to follow the steps below;
When Encountered the problem, if not solve, and more valuable, recorded at once, as the opening of a blog.
First, analysis the problem by myself, based on the existing phenomenon, thinking, then record problem and thinking in notebook.
Second, from the outside world to get experience or knowledge, such as consult others, Google, should learn from them, in the notebook to record the key point.
Then, in the actual use of methods to solve the problem, recorded in the notebook, to flow like water flowing through a channel record in front of the train of thought.
Finally, took the notebook, the above process to summarize into a blog.
problem is the need to summarize,if no problem we should produce problem
When began to study Knowledge, we often see the forest. As the saying goes:
"One tree does not make a forest ", only get more than three trees than have the sense of "forest"
feeling
4, Refused to third-hand technology as far as possible
In the actual study or work, encountered a question that you don't understand, you will need to consult others. If you could get the simple, direct answer from player, cattle people around, it is the best. If you can't, need oneself to find information on the Internet, there may be a problem, there are much information you can search out, but what should be watching is a problem. As far as possible to choose primary material, if you are in a check about GCC compiler options is what meaning, can use man manual, if it is not clear, be checked to the gnu official site, it is best not to literally from blog to get a reprint of the technology. If you're looking for x86 CPU access memory way, should from Intel's official site to find the CPU information, it is best not to literally look for blog on the net to (at least should look at the official material).
Other blog with others naturally understand, but this understanding may have certain subjectivity, sometimes even wrong, should get into the habit of procurement from country of origin. If which day to invent a technology, is this a new technology; If you study in a mature technology, so the technology is used, if you again from a non-source place to learn, so are likely to be "third-hand technology". Needs to consider practical cost, of course, sometimes really can't find the source of material, also don't force yourself too much. In addition, the level of English articles as a whole above the level of the countrymen's article, should try to reading English articles.
5，Distinguish between primary and secondary, locate key point
Everything have a contact in the world, It's unrealistic and unnecessay that describe all contact promblem about the theme of this blog.Personally, a technology blog should be not more than two themes, if more than, you should break it up. There may be many, but minor problems these minor problems are not solved, but must distinguish the priority, which have a great contact with blog theme, should be solved first the small one should be the second solution, even in this blog, not solve. For not solve the problem, can be listed in the "legacy", in the other blog, discussion, give the link.
According to their abilities, cultivate the right level. I stratified holding a technology out the following levels, usually should be at the third level in the blog:
Heard of the technology, to understand what proble need the technology to solve;
Used the technology, familiar with the use of the technology;
Deconstruct the technology, familiar with the technical architecture, principle
Well versed in the technology, integrate the technology with your own knowledge, can use the technical architecture or solve other problems.
6，the style of technology blog
Technology blog is not paper, blog have its practicability. Of course, also have send a paper in blog, such as technology blog author should be the engineers for the most part, rather than academic. A technology blog can be a small to a programming skills, you can write the principle, implementation method, the benefits of the technique, but don't write before 500 after 300 years of history and looking to the future. Technology blog often care technology is practical, and the complexity of non-technical theory behind. Technology blog should not be too harsh, instead of to write the article, and should be the pursuit of small and exquisite
Technology blog should take the indicative mood, personality should be filtered out, technology is not the life complete. Somebody write technology blog, often like to join your mood, let I good bored "" XXX," XXX is difficult, I have continued for two days didn't go to sleep ", to reject the "groan" my personal style.
Avoiding code list. Code is the process of implementation, not principle, list code in order to see the process, rather than for the column code code. My personal habits are listed code less as far as possible, if you can use small space to illustrate principle, never use a big space code. But if the simple list code can be clear at a glance, never waste too much ink to describe the process.
Pictures than text. Pictures with words than simple text easier to understand, or even a picture can omit text, drawing more, less to write is a principle.
Consider the time cost. A blog is basically time in knowledge, faster and faster, so you need to record time is also very necessary.
List problem legacy to for later settlement