Through the accumulation of writing n books, I seem to have found a way to write good technical articles (reply to send me the python stock e-book)

    The books I write are not too few, and the blog posts I write more, but the sales of most books are average. In the technical articles I wrote, although there are more than 10,000 clicks, many of them have only three clicks. Digits.

    Through constant reflection and comparison of some best-selling books and top-level articles, I seem to have found some reasons. In this article, I will combine my experience and the experience of best-selling authors and top-level authors to communicate with you. How to write a good technical article.

1 Choose the right direction and form a series at the same time

    There is a book I wrote about Spring Cloud microservice components, but due to the high technical threshold, the sales volume is average, and the number of clicks on this type of blog post is also average. On the contrary, the Java interview books and interview articles I wrote can be read as stories, so even if the content is not deep enough, the sales and clicks of the book are considered good.

    So if the article is to top the flow, we must find a good direction. For us programmers, how do we choose the direction? To put it bluntly, it's worthless: there are many readers, and everyone has learned the topic of reading.

  1. For example, in the interview direction of my old line, as long as programmers are interested, at the same time, once the interview is completed, you can get real money. In this direction, you can choose "Interview Algorithm", "Resume Skills" and " "Interview algorithm questions" and other topics.
  2. Another example is entry-level articles, such as how to get started with Java and how to get started with Python. For such articles, you can refer to the rookie series. Due to the large number of beginners, if such articles can really help them, it is not impossible to have a high number of clicks.
  3. Another example is articles about earning money and part-time jobs. For example, I wrote books and articles about Taobao's experience in opening a store. They have a lot of clicks. My Taobao opening book has even been rewritten into a traditional Chinese version and introduced for sale by a Taiwanese publishing house. , Better than those technical books I wrote.

      For us programmers, there are many options that can be written like this. After finding a direction, you can even write a series of articles, such as the interview algorithm series, the python entry series, or how to do the public number series, etc., on the one hand, it can continue to attract readers, on the other hand, you don’t need to spend time to find questions, and even more. Use series of articles to build your own brand.

2 The title is neither arrogant nor humble, but generous

    The title is the first impression given to the readers. I think some authors have tried everything they could when setting the title in order to attract attention. It is said that the greater the hope, the greater the disappointment. If the chapter itself does not have enough points to help the readers, then the readers will have contrasts after reading them, and they will not come in the future.

    In fact, the text is as good as the person, such as some technical experts, people who come in contact with it will naturally have a sense of admiration, such as my master, so the title of the article is just right. Generally, the subject of the article is determined first, and then the title is determined. When determining the title, the following methods can be used.

  1.     Use a way to summarize the role of the article, such as "Python Introduction, How to Define Variables", or "Java Algorithm Interview Tutorial: How to Build a Red-Black Tree".
  2.     Use the way of asking questions, such as "How do I introduce my project experience in the interview?" ", or "How do computer freshmen prepare resumes?"
  3.     Use self-questioning and self-answering methods, such as "Talking about the recent feelings of making money from sideline business. First, we must form a system, and second, we must find the platform for blessing"

    At the same time, my feeling is that the title of the article can also be in two paragraphs. The first paragraph provides a foreshadowing and the second paragraph expresses the theme. For example, the title of my article is like this "Through the accumulation of writing n books, I seem to have found writing "How to a good technical article", of course, you can also give the reading direction in the title. For example, in some of my blog posts, it is directly stated in the title, "For Java backend".

    This is the same sentence. When writing a technical article at the beginning, there is no need to consider every word to draw up the title. You have to write the content first. When you have written a few articles and have a heart, the title will naturally be attractive. .

3 Don’t write from the perspective of a veteran, but for a beginner

     I have some articles. When I write, I assume that readers must have a certain foundation, so I didn’t start with the most basic concepts. For example, when writing an article about drawing macd lines in python, I default that readers must have a numpy basis. When Spring Cloud implements Hystrix articles, readers need to have a certain amount of development experience, and the number of clicks on these articles is average. And some articles starting from the basics, such as an article that takes everyone to get started with crawlers, and then how to crawl stock data, these articles have a good number of clicks.

    When I communicate with the editors of the publishing house on the topic of the book, I must first determine the audience of the book. If the readers are set to programmers with 3 years of development experience, then this book will not cover some basic points. If the readers are positioned as architects with 5 years of development experience, or the book will not Talk about basic framework knowledge points. But the current situation is that books that lead beginners to get started are the best sellers.

    This extends to the method of writing technical articles. When writing content and even choosing writing direction, you must not stand from the perspective of seniors. By default, readers are familiar with java grammar and familiar with databases, and can start from a zero foundation in a down-to-earth manner.

    Of course, the purpose of writing articles is for readers and authors to make progress together, so you can't always write without technical barriers. In the end, you must write with valuable skills. So what should I do? You can still use a series of articles, such as the rookie series. The first article takes everyone to get started, the second article uses the first article to talk about technology, and so on. In this way, when writing each article, don't talk about the techniques that have not been mentioned before. When you write the eighth article and the tenth article, you can naturally talk about advanced skills, so that everyone can gain more.

4 Give the code that can be run, or the method that can be operated

    The value of the article is that it can help everyone, specifically it can help readers solve practical problems. For us programmers, the way to solve problems is mostly coding.

    So if the article contains code that can solve the problem, or the operation steps, it will definitely have higher value, so that it will naturally attract readers.

    When I was writing a book, when the editor requested, unless I talked about the concept, I tried my best to show the code, or the operation steps, or the related experience in two pages. And, if you feel that the reader will have problems running the code, such as the need to modify environment variables, or what libraries need to be downloaded, then you must explain in advance. Moreover, if you write the operation method, don't write correct nonsense, try to write something that is operable.

    I won’t say much about the way to introduce code in the article. After all, it’s not difficult for us programmers to introduce code as long as we think about it. So what are the operational steps?

    For example, when talking about preparing for an interview project, if you simply say "the highlight is needed", then it will not be operable. But if you want to go the other way, it means that you can talk about "database tuning experience, OOM tuning experience", and give specific rhetoric, then it has operability. Moreover, this kind of operable text is the condensed experience of the author, so it is more valuable than the code, so if the article contains more such text, the quality of the article will be higher.

5 Proper layout, so that everyone is not tired of watching

    Nowadays, most readers will read articles on mobile phones, so no matter how good the article is, readers’ feelings must also be considered. Specifically, it needs to be properly typeset and not long in length. My experience is given below.

  1.     It can be typeset in a way similar to code indentation, with labels if necessary.
  2.     Use as few long sentences as possible. Each paragraph is generally longer than 3 lines. If necessary, open a new paragraph to write.
  3.     An article should not be too long. If you feel that you are still not enough, you can start a new article or write it in series. 

     And, when the code appears in the article, you can even use the editor to ensure the beauty of the code, so that if the reader is attentive everywhere, the article will naturally be popular.

6 It is best to send resources, so reply to this article and send me the e-book

    As mentioned earlier, if you want to make the article more environmentally friendly, you have to make readers feel rewarded. The gains can be at the code and skill level, but also at the material level. For example, I met some top-tier authors and sent a lot of resources at the end of the article. 

    On the one hand, I am collecting resources. On the other hand, I think that the book I wrote myself contains my dedication to the readers, so sending this can better reflect my sincerity.

    The book to be given this time is this: "Practical Python entry based on stock big data analysis (video teaching version)", Jingdong link: https://item.jd.com/12868774.html.

    Do you think this book will help you?

  •     Able to get started with data analysis and machine learning, and the skills after getting started are enough to deal with basic Python development
  •     Some cases are large enough to be used as examples of curriculum design and graduation design
  •     The so-called ignorant and fearless may be those who do not understand any stock knowledge are the easiest to make leeks. Through the index algorithms and other skills given in this book, they can know the depth of the stock market at any rate. At least they don’t know how to make leeks on the market. 

   When you reply to my article, you can add my WeChat and indicate that you want a python stock book, so that I will give you the word electronic version of this book.

    Some classmates might ask? Why not send paper books? On the one hand, the general practice is to select a few people in the reply to send paper books, which may not ensure that every respondent will receive it. On the other hand, I am also relatively poor. If I were to give each respondent a copy, I would probably have no food to eat, so please forgive me.

    On the contrary, the word version of the e-book sent to everyone can be directly pasted and run. If you really want to learn python, this may be more helpful to everyone. Moreover, the books I have published are not too few, and I am also accumulating materials. In future articles, I may be able to give you more resources.

7 Summary: As long as you work hard and reflect, reaching the top of the article is not a dream

    The top flow of the article is naturally glamorous, but behind this it is more necessary for the author to continue to summarize and write articles with perseverance. Maybe the number of readings for this article is not high, but I won't feel that it's collapsed (in Shanghai dialect, it means losing one's share) and will not recover, and I will be full of energy to write subsequent articles. 

    At the moment, there are many official accounts that rely on high-quality articles to achieve financial freedom, so at the end of the article, I not only wish you all to become technical experts as soon as possible, but also hope that your articles will continue to become classics in the industry, so that they can be achieved by writing articles. financial freedom.

    Please pay attention to my official account: make progress together and make money together. In this official account, there will be more exciting articles.

 

 

             

Guess you like

Origin blog.csdn.net/sxeric/article/details/112658871