As a pursuing programmer, I will not be satisfied with repetitively moving bricks and writing bugs every day. In order to be able to make myself appear more "worthy", I decided to do something very meaningful, and that is to write a technical blog. Because I think "sharing" is the noblest character of our programmers, because when I first entered this industry, countless seniors, through their technical articles with blood, made me avoid many detours. , And stepped on a lot of pits less. Now, it's my turn to give back.
Do open source projects
At the beginning, it was also the most difficult time. Because there is nothing in my stomach, I don't even know what to write.
I started writing a technical blog about March 2018. At that time, it was mainly because I was not very busy at work, so I had free time to do things I was interested in, such as inverting code and blogging. Later, I gradually developed the habit of publishing a few technical blogs whenever I had time. At present, there are more than 70 articles. Since they are all originals, each article takes me a long time to go. Conception and preparation.
At the beginning, I didn't know what to write because there was nothing in my stomach. I want to go ahead. Since there is nothing to write, let's not write it! I don't want to embarrass myself, after all, this is an amateur hobby in itself, and I don't want to make it a task.
Maybe you think I just gave up like this? No, no, you think too much, I won't give up so easily. I was thinking, since there is nothing in my stomach, then the first thing I need to do now is to get something in my stomach first. So the first thing I did was to sort out my experience and insights at work over the years, as well as the code that I used to spare in my spare time.
Since I was more keen to visit GitHub at the time, especially attracted by the superb technology and ingenious design ideas of the great gods on GitHub, I set myself the direction of doing "open source" projects, and the goal was to be able to make them within one year. A project with more than one hundred stars.
Just do it, I immediately started to work on my first open source project XPage . At that time, I could say that I was typing code in the company during the day, and I continued to code after work when I went home from work. I could often type until 1, 2 in the morning. At some point, sometimes I can work until 3 am, and then get up to work at 8:30 the next day as usual. To be honest, I still admire my aggressiveness at that time.
The figure below is the code submission statistics of my GitHub account. From the figure, it is obvious that starting from the first quarter of 2018, the number of my code submissions has exploded exponentially. In the second quarter of 2018, there were 416 submissions, with an average of 4.6 submissions a day, which is crazy when you think about it. After that, it stayed between 150 and 200 basically every quarter, so that on average, there is basically at least one submission every day.
Of course, it’s not enough to write code just bored. I still hope that more people can see what I’ve written, especially open source projects. If no one sees it or no one participates in it, wouldn’t there be any the value of…
Ever since, I started looking for various channels to let more people see my open source projects. Below are the channels I briefly listed (Android):
- Playing Android: https://www.wanandroid.com/ , Hongyang Great God, still under maintenance
- CTOLib code library: https://www.ctolib.com/ , seems to be still being maintained
- Android bus: http://www.apkbus.com/ , it seems to be cold recently, I can’t get in...
- The days I spent on the Internet: http://www.jcodecraeer.com/ , currently half dead and no one maintains...
- Dry goods concentration camp: https://gank.io/ , no one maintains it...
- Developer headline: https://toutiao.io/ , no one uses it now
Judging from the current maintenance status of the Android technology sharing forum above, compared to 2015, Android is indeed a lot cooler.
In the end, after my unremitting efforts and continuous output for 3 months, I ushered in my first open source project XPagewith more than one hundred stars:, which is exactly 9 months ahead of my expected goal! After this success, I strengthened my determination to do "open source projects", and then wrote many open source projects one after another.
Try to blog
After experiencing the initial crazy coding mode and crazy promotion mode, the next thing I need to consider is how to write a technical blog.
At the beginning, because I didn’t have much writing experience, the content I wrote was basically the promotion articles of my open source project. The main thing was to directly move the readme of the open source project, and then add the promotion link at the beginning and the end. almost.
After writing in this way for three months, I found that although the articles are original and full of dry goods, I found that the number of page views of the articles is not a lot, unless the content you write is more famous in the industry Items such as Google’s DataBinding, Navigationetc.
Later, I tried to write a few articles on source code analysis, and found that the amount of reading was even more pitiful. After that, I wrote a few more articles about experience, perception, design patterns, etc., and found that not many people read them.
Choose the right article type
After working for a period of time, I gradually discovered that those articles with high reading volume are basically the following types of articles:
- Headline article. This kind of article titles are very attractive, often with exclamation marks and question marks.
RabbitMQ is so easy to implement instant messaging! Don't even have to write the back-end code?
Please, stop asking me how to learn Java by myself! Confide in
- Practical articles. Teach you to complete a function step by step.
Vue + Spring Boot project combat (1): project introduction
Flutter complete development combat detailed explanation
- Problem-solving articles. Teach you how to solve a common problem in development.
4 ways to leak JavaScript memory and how to avoid
Android to solve the sliding conflict when vertical RecyclerView nests horizontal RecyclerView
- Guide-type article. Teach you how to use a well-known project, tool or library.
The simplest SpringCloud tutorial in history | final chapter
teach you how to use Tencent's hot repair framework-Tinker
- Experience sharing articles. Share personal growth experience, interview experience, career experience, etc.
Database knowledge points summarized in four years of working
life of the program | From Internet addiction teenagers to Microsoft, BAT, byte offer harvester counterattack
- New technical articles. Share the latest cutting-edge technology in the current industry.
Android Studio 4.1 is released,
Flutter upgrade 1.12 adaptation tutorial
Focus on writing skills
In addition to selecting the type of article, the content of the article is also very important, which requires us to pay attention to writing skills:
- The title must be attractive enough.
- The foreword or abstract of the article must be able to arouse readers' interest.
- The key places must be equipped with pictures (the size is best to be uniform), and the pictures and texts can arouse the interest of readers.
- Pay attention to the layout of the article, and the organization must be clear.
- It is best to have recommended reading or related reading at the beginning or end of the article.
Focus on platform features
Sometimes, even if your article is well-selected and the content is good, it may not have been read for many days. Why is this?
Sometimes, for the same article, your reading volume on this platform is much lower than that of another platform. Why?
At this time, the characteristics of the platform are involved. To make the simplest analogy, for the same technical article, your reading volume on CSDN will be much higher than Bilibili, and for the same technical teaching video, your reading volume in Bilibili will be Far higher than CSDN. Obviously, Bilibili is a platform for video, and Zhihu is a platform for Q&A.
Below I will briefly list the characteristics of a few common technology communication platforms:
-
CSDN
veteran technology exchange platform, started as a technical blog, a large number of users, but the quality is mixed. The content of the blog is mainly problem-solving, guide-type, and basic technical-type articles, which is a good place for blog novices to practice. -
Nuggets
Nuggets are a new technology exchange platform, which is relatively popular in the new technology circle. Because of the existence of the boiling point module, it is reasonable to become a holy land for watering. The number of users is small, the content of the blog prefers new technologies, and the overall quality of the blog is high. -
Jianshu
Jianshu, a comprehensive creation and writing platform. Although it started as a non-technical blog, it is loved by everyone because of its beautiful interface. The technical blog content is similar to CSDN, but the overall quality is higher. However, the platform once violated the rules and was invited to drink tea by the new office of the network, so now the review is very strict, and the author is not respected, and all previously published articles are banned at every turn, causing many people to abandon it. -
Zhihu
Zhihu, also nicknamed "Bianhu", started as a knowledge question-and-answer platform. It is a comprehensive communication platform with a high reputation. But since I started as a question-and-answer session, the amount of reading on technology blogs is not very large. -
Think or not
Think or not, also known as segmentfault, is a Chinese version of stackoverflow, a technical question-and-answer platform, the overall bias is front-end, and the number of users is similar to that of the Nuggets, not very large.
In this way, based on the above principles, I began to study continuously, and continuously output articles on major technical exchange platforms, and finally made a little achievement. I became a contracted blog expert of CSDN, and I have gained in Nuggets and Zhihu. With nearly 2k fans, the daily reading volume of articles on major platforms adds up to about 1,000 times.
To be honest, writing a technical blog is not a good way to go. It requires your unremitting efforts and unwavering belief, otherwise you will easily give up because of some trivial matters.
Operate WeChat Official Account
After doing some time technology blog modicum of success, I did not start slacking off, then I find those bloggers do well already begun running its own micro-channel public number, so I without thinking, in a micro-channel public number After filling in a bunch of information on the official website application form, I started my WeChat official account.
When I started writing my first article and opened the WeChat official account article editor, I was dumbfounded: because before that, I used the Markdown editor for blogging, and the WeChat official account does not support this editor. . Not only that, the WeChat Official Account Editor has strict regulations on links in articles, and links to articles on non-WeChat Official Accounts will be invalidated.
But in the final analysis, these things can be overcome, but the most difficult to overcome is the flow problem. Since the WeChat official account articles are not open, there is basically no reading in the initial stage of creation. The second is that even if you have a few followers, the click-through rate of the WeChat official account article push is very low, and a click-through rate of 20% is already very good.
Although the WeChat official account has many disadvantages and is very difficult to operate, it is still very good to use it as a management and drainage platform for my open source project materials because it has functions such as automatic replies, custom menus, and hashtags.
to sum up
- The premise of writing a technical blog is that you have to have real talents, otherwise the things you write are simply misleading. Therefore, it is the first priority to improve one's technical level.
- Before writing a technical blog, it is best to clarify your own writing theme, so that what you write is more attractive.
- It's important to choose the type of technical blog, and you need to pay attention to writing skills.
- The characteristics of different communication platforms are different, and the suitable writing content and methods are also different. In the chosen platform, choosing the right writing method and content is very important.
- The operation of the personal WeChat official account is relatively difficult, but it is still very good as a platform for the management and drainage of open source project materials.
Resource sharing
Below are the good tools and platforms that I have used on the Poiteng blog in the past two years. I will share with you for reference only.
Open source project hosting platform
- github：https://github.com/
- gitee ：https://gitee.com/
Technology Exchange Platform
- CSDN：https://blog.csdn.net/
- Nuggets: https://juejin.im/
- Think or not: https://segmentfault.com/
- Short book: https://www.jianshu.com/
- Know: https://www.zhihu.com/
- Bili Bili: https://www.bilibili.com/
- WeChat public account: https://mp.weixin.qq.com/
Tool URL
- Markdown article layout tool: https://www.mdnice.com/
- Free picture bed (upload picture): https://img.rruu.net/
- Alibaba vector icon library: https://www.iconfont.cn/
- WeChat public account plug-in (yiban assistant): https://yiban.io/
- Forage QR code generation tool: https://cli.im/
- Online ps tool: https://www.uupoop.com/
- Application distribution platform Dandelion: https://www.pgyer.com/
- MP4 to GIF tool (mac): https://github.com/mortenjust/droptogif