Hello, welcome to the online roundtable activity themed “Technical Writing”. Let me introduce myself first: I’m Boiling Point Operations, Steam, and I’ve invited seven of the most representative writers in the Nuggets community to talk about their views on “technical writing,” The purpose of this roundtable is not to get you a 1K + like or 10W + read article, but to give you a sense of what the community’s highly read and well-followed authors think about “technical writing” and what tricks they use to make technical writing “successful” in the community.

As the core of the community’s content production, these writers have a better understanding of the tone of the community and what works best for the community. If you want to achieve the same technical “success” as them, listen to their thoughts on these issues.

Let’s take a picture of them first

The guest is introduced

Come and nuggets guy partners to introduce themselves 😊

Hi, MY name is Superman Wang Xiaojian. I have been writing for 5 years, covering algorithms, artificial intelligence, big data, various development and other types of articles. I have published “Anatomy of Tomcat Kernel Design”.

Hollis: I am Hollis, a personal technology blogger and the person in charge of the wechat official account Hollis (ID: Hollischuang). I have read millions of technical blog posts and written technical articles for more than 3 years.

J_Knight_ : Hi, I’m just over 3 years non-professional iOS developer, I’ve been writing tech blog for over 2 years now and have accumulated over 11,000 followers on Nuggets.

My name is Liu Zhijun. I am a Python developer. I have been taking notes and blogging since I was in college.

Liu Wangshu: I started to write blog in CSDN in 2011, and then I became an expert in CSDN blog. Then I attracted editors from publishing houses through CSDN and published two best-selling books “Advanced Light of Android” and “Advanced Decryption of Android”. At the same time, I also opened my own public account [Liu Wangshu]. The average reading is 2000+.

I: Hi, I’m Waiting, a front-end developer. I have three years of working experience and I should have been writing for one and a half years.

Hu Yui: I’m Hu Yui, a brilliant and handsome elegant Web front end raider, a gold-mining user who didn’t make his fortune nor his fortune with his JavaScript series, JavaScript Specials series, underscore series, ES6 series.

Round table began

What do you gain by writing?

Superman Wang Xiaojian: improve exploration ability, thinking ability, expression ability, perseverance.

Hollis: Similar to Superman Wang Xiaojian, IN addition to improving my ability to express myself, I also improved my technical ability and gained recognition from many fans.

J_Knight_ : What I gain from writing is not only the fans and influence of the platform, but also the ability to learn, the ability to describe in language and the quality of striving to make things the best. For more details, see my latest post: What have I Learned from tech blogging? – J_Knight_

Liu Zhijun: WRITING has brought me a lot of benefits. It helps me to reorganize my thoughts, get more attention and communication opportunities through sharing with others, and get job opportunities and invitations from some publishing houses. At the same time, I can earn some extra income through writing because I have caught up with the good times.

Liu Wangshu: As I introduced myself, I published two best-selling Android books and was invited to attend many technical conferences and gave speeches through my bestselling books. I got to know a lot of well-known celebrities and technical experts in the Field of Android, and also made many Android developers know me. As you can see, writing has not only improved my technique, but also generated a lot of positive and qualitative chemistry, which has helped many developers.

I: Compared to them, my writing time is a little short, but the biggest benefit of my time in writing is learning from other front-end developers. As well as their own knowledge points of a learning, sorting, summary. I will continue to write in the future. I hope you can give me more support.

It seems that you have gained a lot from your writing. What is your original intention of writing?

Superman Wang Xiaojian: express personal opinion, establish personal brand.

Hollis_ Public account Hollis: Record and share knowledge to enhance personal influence.

J_Knight_ : My original intention of writing is simply to record some study notes and reading notes. That is still the purpose, but as the number of followers increases, the quality of the blog has become more demanding.

Mr. Liu: Didn’t think too much, the earliest writing is to treat it as a tool to cheat, I early is to put the things written in the local, but it is not convenient for local in other places to see, then the content directly on the Internet, to become a blogger, the start writing is very bad, every time when looking back on it even oneself also don’t understand, This is a problem that many of us have when we first start writing, because we don’t think about our readers, and we write on our own. Writing is now more of a thinking process than a memo.

Liu Wangshu: every time to see the article on the net, see the awkward, on their own to write, see their own writing is the most comfortable, but also can constantly improve.

Waiting I: Originally, this was just for personal notes, but then I decided to share my notes, communicate with others, and have a technical blog, plus my resume, so I started to write an article.

Hu Yu: I hope I do front-end in a few years (the future whether do back-end, or do management, or set up a teppanyaki stand is a far away from the front-end), can leave a little something to the industry.

Summary: It seems that everyone’s original intention of writing is similar, which is to share and organize content and build personal brand 😊

In the perspective of steaming, articles can be divided into series and single articles. How do you choose a topic for a single article?

Extension, everybody is written “made a Vue imitation xx”, “you ought to know about Javascript closures” all common topics such as articles, along with the increase in base of the article later articles without new breakthrough point is difficult to obtain high reading and high praise, so how to writing a cut to a certain point to a single technology is a difficulty.

Superman Wang Xiaojian: In addition to writing a book, I write a single article topic mainly from three sources:

  • I will write an article about the things I am responsible for at work.
  • When I get inspiration, I will send key points to my wechat and record them. When I have time, I will look at the ideas I have sent to myself and write.
  • Reading freely, because I ask myself to see more than 30 or 40 books every year (the study has been filled with hundreds of books), so after reading a lot of books, I will have a lot of personal opinions or summary, so I can write an article.

Steaming: Well, work-related content is not easy to “clash”, the uniqueness of content comes from work and books.

Hollis_ public account Hollis: Problems encountered in work, summary of learning, questions from readers and fans, etc.

Steaming: It seems that writing the problems encountered at work is a great source of articles. Let’s see what J_Knight_ thinks about this 🎙️

J_Knight_ : Apart from some source code parsing articles, my blog is all related to the business aspect of learning at that time. Some unexpected business requirements may involve unfamiliar technical points, so you can choose topics related to this area. So many of my blogs are not written from scratch, they are from my own daily study notes. After the study notes are formed and then you revise and add your own thoughts, the blog is almost formed.

Steaming: As J_Knight_ says, book notes are a good starting point to learn to summarize and organize knowledge points over time.

Liu Zhijun: I didn’t choose the topic deliberately, because I’m not a professional writer, my article materials generally come from work or through the accumulation of reading habits, gradually form their own material library, free from the material to choose a theme to write.

Steam: the origin of zhijun teacher and xiao Jian big guy is similar, what do you think about this?

I: I think it is important to know what technical topics I am currently interested in and what technical topics I have mastered or studied before WRITING. Do not choose some unfamiliar topic. As for whether it is a series of articles, I don’t think it has much to do with it, but one thing to pay attention to is that the topic is not suitable for too broad, too broad may lead to too long articles, readers will be tired, write tired, will be messy.

Steamed: wait said some topics taboo points Hu Yu have what supplement?

Hu Yu: Even though I never write individual articles, I feel like IF I write an article I write what I want to write, or what I learned recently, or what I thought and practiced from my projects. These topics don’t need you to think about them, they just come out of my mind.

Summary: We agree that the topic selection of this article comes from work and reading books

How to deal with digression in the body of a technical article – questions from the pastProblem to collectIn “but the qing mei smell” of the question

Many tech blogs will inevitably include some of the author’s own feelings (or digress). These words can sometimes be called “blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah.

Hollis_ Public id Hollis: Control the word count and paragraph. No more than two paragraphs, no more than 500 words.

Steaming: control length seems to be a good method, but specific to the article, is probably to control the ratio. However, J_Knight_ seems to have a different view 🎙️

J_Knight_ : First of all, I think there should be as little as possible, or even no words with personal feelings. Such words will show that the author is not professional enough, and will affect the professionalism of the whole article, and the quality of the whole article will be greatly compromised. It is painful for a professional article to be dragged down by emotional remarks and digressions. And it doesn’t have to be used as a segue or to make the reader feel like a substitute. Instead, it’s perfectly ok to use objective, professional writing as the transition.

Steaming: Teacher Zhijun also has a different opinion, 🎙️

Liu Zhijun: There is no need to deliberately grasp it. Behind the article is a real person, not AI. People have temperature and emotions. If you are deliberately adding drama to the article, the reader will appear to be wordy.

Steamed: 🤔 to understand the article from the heart do not know appropriate, listen to The view of WangShu to this problem.

Liu Wangshu: I think technical articles or less mixed with some personal feelings, just like writing a book, as far as possible to be concise and comprehensive, can be brought over, never drag.

Steamed: seems waiting and Wang Shu, J_Knight_ the same view?

I: Yes, with regard to personal feelings, personal advice is: avoid it if you can avoid it, say it in one sentence if you can’t avoid it, and famous is personal advice, opinion, etc. Emotional views should not be too extreme and individualistic. For example, as hot pot soup bottom can be hot or not hot, like hot pot soup bottom can express their preferences, but it is not recommended to not hot pot soup bottom criticism.

Hu Yu, how do you look at this issue of hu?

Hu Yu: Emm, I never write.

Conclusion: Most authors choose not to write when they can.

Write source code interpretation or theoretical relatively strong article, how to take into account lively and interesting? — Before the questionProblem to collect”Frank’s Cat” & RecoReco

Hollis: Telling stories, metaphors and drawing pictures

Steaming: Drawing is really a great way, illustrated articles are always very popular, pictures are more intuitive than words, readers can better understand what you say, the same is true for metaphors. J_Knight_ has something to add 🎙️

J_Knight_ : There are quite different ways of writing these two kinds of articles. I will explain them separately here.

  • A. Source of reading class article: this kind of articles must avoid the analysis and interpretation of the large section of the code, so attention should be paid to in order to avoid let readers feel boring, need in the interpretation of the source code before you introduce the source or general framework of purpose and method of use, let the reader to its functions have a preliminary understanding. Then provide an architectural diagram of the framework and explain the role of each member or module in the framework. This is to give readers a sense of the structure of the source code. And when interpreting the source code, it is best to use graphics or day output to let the reader really see with their eyes what the code is doing. Finally, being able to give a reason why the framers did it the way they did it (what are the benefits of doing it, and what are the problems of not doing it) can significantly improve the quality of your blog. I think if you do this, you can avoid the reader feeling boring. You can refer to a source code interpretation I have written: MJRefresh source parsing. While explaining the code, this article also provides many visual screenshots to help with the code parsing.
  • Two. Theoretical relatively strong article: this kind of boring words to avoid relatively easy, simply say a word: theory combined with practice, abstract into concrete. Don’t just write a long paper about your theory, but use a working Demo or a piece of code to verify your ideas, preferably in a visual way, with graphics or daily output, so that the reader can really see what the theory does and what the theory means. You can refer to my article on design principles: Six Principles of Object-oriented Design. In addition to introducing these six principles, this article also provides Demo and UML class diagrams for them; It also compares the difference between following and not following these principles.

Steam: very detailed introduction of the source code and the writing method of the theoretical article, zhijun teacher of the theoretical article what opinion?

Liu zhijun: For theoretical things, it’s best to use metaphors. Good metaphors can make readers understand in a second. I have written several examples about proxies and reverse proxies, as well as the concept of Python decorators, which have more than 1,000 likes on Zhihu. In addition, a picture is worth a thousand words, and many Technical books in Japan can present advanced content in a graphical way, which is a good example

Steamed: consistent with Hollis, wang Shu seems to have a different view? 🎙 ️

Liu Wangshu: Take Android system source code, in fact, I also want to write vivid and interesting, but in fact this kind of theory and vivid and interesting completely do not take the edge, hard together will only let the article lost the original luster.

Steaming: it seems that vivid and interesting is not all content can be done, 😊, listen to wait how to see vivid and interesting?

I: Both vivid and interesting give me a feeling, the first to avoid a long paragraph of text. Secondly, some pictures should appear from time to time to make the article lively. Considering both of these two points, what impressed me most was “The Transformation of The Code Farmer”, in which the article cited a large number of animations and pictures, making the article more interesting. I still remember that I have seen an article in the form of teacher and student questions, but the article seems to be deleted, can not find. These two forms can be referred to. It’s a way for me to learn.

Steamed: “code farm turn over” a very good book, read this article partners have the opportunity to read Hu See Yui interpretation of the source code how to see 🎙️

Yuba: the source code interpretation itself is a reader through a reading can understand things, I can only do the process of understanding the source code, readers may encounter problems, may think of problems are write his understanding, and then…… And then I let it go…

Steamed: 🤔Get to the point is to share their views to help others understand

Summary: Vividness and fun can be achieved through diagrams, but sometimes it is unavoidable to explain the source code and theory in a “boring” way, presenting your own understanding to the reader for reference.

In-depth technical articles have a small audience, how to balance technical depth and high reading? — Before the questionProblem to collectWujunze & Min Xiansen & Sea_ljF

Hollis_ Public account Hollis: Try to use popular words to express the difficult technology clearly, step by step introduction, with code, pictures, even animation, audio and so on.

Steaming: auxiliary graphics, audio form, step by step from simple to deep explanation.

J_Knight_ : “High snow, low people”, it is a very normal phenomenon that the audience of in-depth technical articles is not very deep. I have never written a very in-depth technical article, but for this kind of article how to improve reading, here is my own opinion. In fact, high reading comes from two points:

  1. The title looks attractive and easy to click on
  2. Many people can gain something in the article and are willing to share this article

Let’s talk about the above two points respectively:

  1. Headlines look appealing for two reasons:
    1. The theme does not stray too far from the current hot topic
    2. The first is that the subject matter should not be too one-sided. If it’s too far off, most people probably won’t click, like one. The theme of NET is definitely not the same as the theme of Flutter. The second is appropriate to add some fascinating rhetoric, but do not recommend too much, because it will affect the overall professionalism.
  2. There are a lot of people who can learn something from the article so it’s about both technical depth and learning. I think it’s the hardest part: it’s a great sign of a writer’s skill to make obscure theoretical knowledge accessible to a large number of people. Here are two tips:
    1. Provide sufficient background information
    2. Use metaphors and associations to provide plenty of background: You need to imagine the reader as a complete layman, and you need to provide him or her with all the background he or she needs to know first to build the body of knowledge that you will explain later. Make use of metaphors and associations: even background knowledge is enough for the reader to understand on a theoretical level, but it’s not enough. Because at this point the reader may not be applying them. Therefore, it is best to use real examples or imagine a vivid example to simulate the theoretical model, so that readers can have a more vivid understanding of the theory.

Steaming: excellent writing skills, teacher Zhijun has another interpretation of this problem 🎙️

Liu Zhijun: People are more willing to receive things that do not need to think about, which is also the reason why in-depth technical articles do not attract so much attention. If you want to get better reading, it depends on how well the author understands the technology, and the more you understand the technology, the more likely you are to express it in plain language.

Steam: Zhijun teacher said quite right, combined with my own, some depth of content is eager to be broken down into bits and pieces I don’t need to think to read, 💦 my personal reading habits is not good, fortunately, I have such readers to the knowledge point of profound understanding of the people to output content 😊 see WangShu look at this problem.

Liu Wangshu: I think as a writer, certainly hope high reading. As writers continue to improve their skills, most of them will still want to write in-depth articles, and as more and more people enter advanced development, these in-depth articles will also be well read. In addition, some new technology entry depth is not high, but you will get high reading, you can write, after all, technology is not only to pursue depth, but also to take into account the breadth.

Steaming: wine is not afraid of alley deep, time will bring flow to good content, this is true, although slowly but eventually will be received, spread. Hu Yu seemed to see it differently.

Yuba: It’s hard to do that, so don’t even think about it. I learn what I want to learn, I write what I want to write, and I share it, and if it helps the people who read this, I’m happy, the amount of reading, whatever, so be it

Steaming: let nature take its course is also good, waiting for how to see? .

Waiting I: Since the article is technical depth, so understand the article fewer people, reading will be affected. It seems difficult to combine technical depth with high reading. What can be done is to do as much as possible in an article, in a lively and interesting way, the depth of the technical expression is easy to understand, so that more readers can easily understand, there will be a rise in the number of reading, this seems to go back to the last question (how to give consideration to lively and interesting?) .

Steamed: It is true that in-depth content requires high understanding of people, and the corresponding audience base is small, so the reading volume is not as high as popular articles.

Summary: for the balance of high reading and depth, the guests’ views are completely the same, the views of steamed biased Wangshu, Hu Yu, personally feel straighten out the mentality, focus on writing is good, time will be good or bad.

Is there any writing tool amway?

Hu Yu: I also want to see what other guests say?

Superman Wang Xiaojian: Let’s write articles mainly for content. The tool is just to improve efficiency. Markdown is very efficient, and it is convenient to display code and typesetting, and most websites support it. So just need Youdao cloud note + Chrome’s micro blog graph bed plug-in can be very efficient.

Hollis_ public account Hollis: MWeb — “MWeb” is a Mac Markdown application that has attracted a loyal audience due to its rich features and powerful ease of use. With “MWeb”, you can write, take notes, generate static blogs and more. Official site: Portal

J_Knight_ : Writing tools I mainly use the following: – Markdown notes: Evernote or Youdao Notes. Both of these notes support multiple platforms, so it is very easy to update. You can use your mobile phone instead of your computer. And there is no limit to computer clients, because Web services can be used. – Tubed: I originally used Qiniu, but later the domain name was reclaimed, so I changed to use ali Cloud OSS service. The service charges by data, but my data is not very high, and I only use a few cents for half a month, so I feel ok. – GIF creation: Sometimes you will need to use giFs to present a Demo. I use PicGif (Mac). The first step is to use the Mac’s own QuickTime to record the Demo, and then use PicGif to edit it.

Liu: I don’t use a lot of tools, I write locally with Sublime, stored in a private repository on GitHub, and write based on Markdown so I don’t have to spend too much time on layout. The simpler the tool, the better. I’m a heavy Markdown user.

Liu Wangshu: Visio 2013 is recommended for sequence diagrams and ProcessOn is recommended for other diagrams.

Do you have any notes to share with us in writing? For example: layout, code presentation?

Hollis_hollis: Respect others’ intellectual property rights.

If you find someone else’s article is not original, it comes from someone else and appears in his column without labeling, remember to tell the official ~ Thanksgiving ❤️

J_Knight_ : I think there are a few things to note in writing:

  1. The level of the headline should not exceed 3, otherwise it will increase the cost of reading
  2. If there are parallel items, it is better to write them vertically, not horizontally, starting with 1,2,3 or origin.
  3. Explanatory languages are best marked with markdown’s reference syntax, which allows users to directly distinguish between text and auxiliary statements.
  4. The combined height of the code block and the description of that code cannot exceed the height of a screen. This is a problem with the reading experience: if the code block is too long, beyond the height of one screen, the reader might scroll up and down, affecting the reading experience. Also, it’s not easy for the reader to see the explanation of the code, and the screen may scroll up and down, which is also a bad experience. Therefore, WHAT I recommend is that the code snippet and the explanation of the code be fully displayed at the height of one screen, so that the reader can see both the code and the explanation at the same time by moving their eyes.
  5. If the theoretical knowledge of the article is too much, it is best to provide Demo or log output, so that readers have a more intuitive understanding of the theory.
  6. Paragraph to paragraph, especially between each part should have a transition sentence, otherwise the reader will have a very abrupt feeling, affect the reading experience.
  7. The description of the text should stand up to scrutiny, avoid by all means mechanically, it is best to use their own words to express the text of the data or other literature. That means you need to really understand what you’re writing.

Steamed: some great writing summary, underline, write down 📒

Hu Yu: I will obey the writing specifications of technical documents in Chinese, I don’t care about the rest.

Steamed: ruan teacher’s writing norms quite complete.

Finally, how do you combat your reluctance to stick to writing? — Before the questionProblem to collect”Pea flower under the cat” question

Superman wang Xiaojian:

  • habit: Cultivate writing habits, habits of a few days do not write the whole body uncomfortable.
  • Make a plan: You can set short-term, medium-term and long-term goals for yourself. For example, you are required to write five articles in a month, write a series of articles in a certain field in half a year, and write a book in two years.
  • Set aside fixed timeWriting a high-quality essay takes an average of four hours to complete, so you must ensure your writing time. For example, you can set aside 8 p.m. to 10 p.m. on Monday, Wednesday and Friday for regular writing time, and set aside 3 hours a day on weekends.
  • Continuous output: Find a platform, such as Nuggets, CSDN, public account, etc., to ensure at least weekly frequency, with the feedback and encouragement of fans and readers, can also make yourself more motivated.

Hollis: I push myself, like when I do my own account, and I make it a goal to do something original every week. This will force you to constantly produce original output.

J_Knight_ : I think the root cause of inertia or procrastination is the perception that the implementation cost of doing something is too high and the payoff of doing something is not predictable.

Coming back to blogging, many people have similar reasons for not wanting to blog or for not being able to do so:

  1. No subject, no direction, no place to start
  2. It takes too much time to write a blog, and even if you do, it takes too much time and energy to write it well
  3. Blog writing quality can not be guaranteed, afraid of being teased.

In fact, none of the above three points seem to me to be a problem:

  • As I mentioned in the above question, most of the blog I write comes from my study notes. So as long as I have been studying and taking notes, I will continue to refine, improve and finally form a blog as long as I have time.
  • I think it takes too much time and effort to write a blog. In fact, the time from a note to the final formation of the blog is not very long. It is just to add some excessive writing for the reader, and maybe some illustrations. Proficient words can be immediately out of a blog. This needs to mention a time management problem, many friends like to use more than one block of time to write a blog, or a blog to be completed at one go. These thoughts are unnecessary: first, blocks of time are precious and should be used to study and think. On the other hand, when you write a blog post, you may read it the next day and feel like there’s something you can improve on. Therefore, I personally suggest using fragment time to write a blog: you can use cross-platform note-taking software (youdao Note and Evernote both support Markdown syntax) to write a blog. When you have time, you can open your computer or mobile phone to read your notes. If you want to modify them, you can modify them in time to improve the efficiency of time use.
  • In fact, there is no need to be afraid that the quality is not up to the requirements. There are two benefits to writing articles with low quality or errors:
  1. Someone may come and correct you
  2. Allow others to see your growth
  • There may be someone who will come and correct you: and there may be someone who will patiently teach you and correct you when you make a mistake. But if you do not write down your understanding, you may not know for a long time that what you understand is wrong. The greatest fear of learning is not knowing that you do not know, so it is not necessarily a bad thing to expose problems as soon as possible.
  • Allow yourself and others to see your growth: The blog is actually a record of your own learning and growth. As a reader, you can feel the growth and carefulness of a blogger when you see a blog that continues to grow. Not all of us start blogging when we’re really strong. Many of us start from scratch and build up over time. Because writing is also a kind of skill, as long as more persistence, more thinking, ability naturally better and better. It’s not how you started, it’s how much you grew. So don’t be afraid that the quality of your blog is not good enough to write.

Qing Zheng: Well, the analysis of three reasons is quite in place, and there are corresponding coping methods. See how zhijun teacher who has been writing for 7 years dealt with 🎙️

Liu Zhijun: Execution is the key, first set a achievable goal, for example, make sure to write an article every week, after writing, treat yourself as a reader, read several times, until the modification into their own understanding. If the effect is good, you can try to contribute to the website or the public account to get more exposure opportunities, which is also a positive incentive process. Once you have positive motivation, you will be motivated to invest more time in it and it will become a habit.

Steam: Continuous output should also have a little incentive, as a platform we will strive to provide exposure and traffic to quality authors and content, listen to wait how to think about this issue 🎙️

Wait I: is my own story, start writing, wrote a few articles, as long as there is content to write, as long as there is to learn new knowledge, or work out some tips or even black technology content, will take notes on your own, made notes, and organize the next article also won’t too far, should not be because of lazy don’t want to insist on writing. When you are used to writing and have content to write, if you do not write, you will feel that you have something to do and feel uncomfortable all over. There are three reasons why I don’t want to insist on writing.

  1. I’m too busy to write
  2. Articles are read too little and lose interest
  3. I don’t have anything to write about right now. For the first two reasons, mainly look at their own actions, because time can be squeezed out, the beginning of the article was read too little is normal, write more, popularity will improve, if not, may have to think about their own article is not where the problem. The last one should be a problem that most people will encounter, which is also the problem I encounter now. There is nothing to write. It may be because I have encountered a bottleneck in my study, or the knowledge points in my study remain unchanged. This situation can only rely on their own to overcome, learned new knowledge, should have content to write. Personally, THE reason WHY I don’t ask myself how many articles to write in a month, or how many articles to write in a year, is because writing is influenced by time and content. If forced to write, quality content is average, but feel it is better to wait a long time to write, write better.

Steamed: it seems waiting and J_Knight_ have a similar view, see hu hu has been very Buddha department how to look at this problem.

Hu Yu: Yui, I want to write write, don’t write. Writing enthusiasm itself is a process of ups and downs. When you want to write more, you will have a good rest when you don’t want to write. Deliberately asking yourself will only increase the fear and disgust of writing itself.

End of the round table

That’s the end of this round table on technical writing. Don’t hurry:

  • We also invited some of the most popular authors to talk about what they think about technical writing

Keep an eye out for comments in the comments section between 2019.01.09 and 2018.01.18

  • If you can’t get coverage for your article, please post your address in the comments section and ask your friends in the community to help you analyze the reason

Only when you contact the reader will you know what they want to see and where your article needs to be improved ❤️.

read

It includes the views of community partners on “technical writing”

  • How to Write a great Tech blog post
  • The tech blog thing