Preface:

Hi everyone, I haven’t updated you in a while, I can’t remember exactly how long it’s been, but today we’re not going to talk about technology but we’re going to talk about why programmers keep blogging, and without further ado we’re going to start.

Personal view

I’ve been blogging on and off for a while now (about a year on mobile and cross-platform), and I’ve been working as an Android mid-level developer for over four years and I’m starting to get my feet wet. I have to say that blogging has changed me a lot, so as a technical person (programmer), why do I feel compelled to keep blogging? Here, let’s talk about some of my understanding and comprehension.

The benefits of blogging

  • No matter where you write your blog, blog park, CSDN, your wechat official account, or weibo, I think it’s ok. First of all, blogging as a more formal, objective and authentic resource for sharing technology strikes me as something that really should be formal. It’s not so much about emotional intelligence. It’s about academic accumulation and open source spirit.

  • Blog should feel like a very proper way to learn. It is a form of summary, which you can refer to, copy and paste, but because it is a very formal article, you have to straighten out your summary and process and correct the typos in the article. It can correct the attitude of a technician. This is a hidden benefit.

  • Thirdly, we have been singing the nursery rhyme “a good memory is better than a bad pen” since childhood. However, with the advent of the information age, paper and pen are gradually replaced. How can we keep records when we are dealing with computers? Yes, I think youdao Cloud note, Evernote, Word document, even TXT file is no problem, as a knowledge recording tool, blog has the same purpose of recording, it can help you remember those: Complex technical principles, snowy command messages, confusing front-end labels, various language features, and basic knowledge forgotten again……. It remembers everything

  • I started out as a non-professional programmer, so I didn’t have a lot of power to interview. I left a company in the software park in the middle of 2019. I went to a bigger company for three rounds of interviews and chatted a lot with the interviewer. I also included my blog address and Github address on my resume. The interviewer is also very value my personal ability Every day I just got the offer in the interview process with half of communication source technology basic knowledge itself half source to determine your personal learning habits Insist on writing a blog can really give the interviewer if you are a good impression At least not bad In the technology doesn’t open big gap is time This is a plus and a shining point.

How to Write a Blog

Let’s talk about how to write a blog

This is also a lot of programmers are very troubled by the problem, many programmers will tell me about Teacher Xu. I can not write technology home in fact, this is not the point, not who will write Hongyang Guo Lin Ren Yugang these god bloggers are from the small white over, we should be brave to take the first step is the key. We can start with a summary of the simple things, they are ok.

The title

Since most blogs are public, your blog is not just for yourself. Others will search the Internet for keywords and may come across your technical blog. A good title will define your blog theme. And this is one of the things that I’ve learned as I’ve been writing about it is that it has to do with the language technology stack you learn android front-end IOS or back-end and you put the name of your technology stack in your signature and then you put a space in the title of what you’re going to publish

The article structure

The structure of the essay should be as clear as possible. You’d better give each section a subtitle and type them H1, H2, H3. This will help you and other readers quickly locate the information they need, which is especially important for a long blog post. Secondly, you should think about the content of the article beforehand. Organize your language and logic in a rhythmic way. It may take a while, but considering you’re a perfectionist, shouldn’t you do it?

Figure captions

If you’re writing front-end mobile or cross-platform then you should at least include screenshots or GIF renderings so that the reader can read them.

Language is smooth

Most technical personnel may not be able to talk well, so practice writing and express your ideas clearly and clearly on the blog is also a personal ability. When I look up other people’s blogs, I often see articles that are poorly written and illogical. This article, I really don’t see the desire , of course, is not to say that we at the time of writing a blog even should not have a wrong character, but should always remind myself to attach importance to his own blog, want to let the person reading your blog to learn, a not smooth, big thoughts, even no head no tail doesn’t help that the others. A little bit of a trick here because typing on keyboards is very fast these days and it’s hard to avoid typos when you’re in a hurry. So when we finish writing an article, there’s a preview mode on the right of Markdown. We read the article three times and check it

There better be a result

Blogs that address specific problems tend to briefly describe the problem and then offer solutions, but don’t post successful results. What I suggest is to put your results out there for everyone to see. When I’m looking for a problem and I see someone else’s article and the same solution doesn’t work at all, I have a deep suspicion that the person who wrote the article didn’t work either. Therefore, a screenshot of the test results shows that the solution to the problem works, which further confirms the usefulness of your blog and increases the credibility of your blog.

Conclusion language

After finishing the article, we will make a simple personal summary of the content of the article and add some personal views and opinions (not all of them are correct, but there must be some or it will give people a feeling of rotten end). It takes at least a couple of days to prepare an acceptable post

  • Write source code demo
  • Understand the implementation principle of source code
  • 3 blog writing and code paste and code implementation explanation

So the downside of blogging is that it’s very time consuming for single people like me and painful for those of you who are married or in a relationship. These are my personal views and not everyone’s

The final summary

I’ve been asked why I have to do this kind of thankless work but it seems to me that a lot of things are about having your own beliefs and staying true to your roots and loving learning open source rather than being lazy and taking shortcuts is writing code the same as reading books, There is no shortcut to (paper from night light I never know this matter to practise) please those who like to take shortcuts, you (mind your own mouth Everyone has their own way of life and the way of learning and achieve your dream, finally I hope my article can help you solve the problem, I will contribute more useful code to share with you. If you think the article is good, please pay attention and star. Thank you!

About Blogs (address of major Blogging platforms)

CSDN: blog.csdn.net/xq610928?sp…

Jane: www.jianshu.com/u/40d2aa647…

The Denver nuggets: juejin. Cn/user / 123990…

Blog: garden home.cnblogs.com/u/xq9527

github: github.com/xq19930522