My public account writing experience sharing

On July 09, 2021, the number of readers of the Public Z number reached 1 week, reaching the first small milestone. (Pen core@All lovely readers)

On April 26, 2019, I published the first article " SpringBoot and RabbitMQ Detailed Explanation and Integration ". At that time, the update frequency was very low, and I might not update an article in a month.

Before I knew it, I had been writing for 2 years.

When I first wrote it, I could see that the article was very young, the typesetting was uncomfortable, and the style was just like a document, not smart enough.

Nowadays, readers and friends praised: "Brother Ma, your article is very well written, the content is hard-core, and the graphics are beautiful. Are you an architect who turned to art?"

From 0 to 1 w, it lasted 2 years. After continuous writing and learning writing skills, I would consult other talents to get the current effect and praise after seeing the beautiful pictures.

Among the hard work, only I and a group of account owners who insist on writing official accounts have a deep understanding.

Most importantly, all of this is worth it.

are derived from a small action "click to follow" by readers and friends. It is you who gave me the motivation to continue to output good articles.

Today, let’s talk about my mental journey and future plans since I wrote the official account.

Why write an official account

At first, it was called "JavaStorm", which was used to record the study notes of Ma Ge. To be precise, the time when the official account "Code Ge Byte" really gets its soul is 2020.

"Code Ge Byte" comes from Megabyte megabytes. It is used to metaphor every word, every idea, every little bit of knowledge in the article, and finally gather every good article, which can withstand scrutiny.

1 GB comes from the accumulation of 1024 MB, and good text comes from the accumulation of every word in "Code Ge Byte".

Megabyte directly is not friendly enough, nor creative.

So deliberately wrongly written as MageByte pronounced as "code brother byte", and be friends with readers to get closer.

The original intention of creating an official account was because I paid attention to a lot of official accounts, saw many technical articles, and found that some authors wrote really well: shared interviews, programming skills, architecture design, source code analysis... let more development The person grows.

Some are very casual and have no depth, the title is party, and even the obvious mistakes are misleading...

There are also some high-quality publishers who output high-quality articles and turn them into advertising hydrology...

Ever since, there is a "code brother byte", through writing to improve their writing ability, through continuous output to force oneself to input.

From passive learning to active learning, you might be able to become a self-media creator in the future, so why not do it as a sideline of your own.

At the same time share their own technology and development experience and programming skills, write good articles to allow more IT developers to grow.

"Hardcore articles, poetry and distant places" is my aim. I hope to bring value to every reader and grow together. When you are unhappy, write some humorous articles have fun together.

Hard road

In 2019, I wrote an article on design patterns and algorithms. At that time, I was still in the writing learning stage.

Don't know how to write at the beginning? How to choose the topic? How does the title start? How to clarify what you want to express? How should the content of the article be organized?

What am I going to write? Writing an article is not a study note. You need to clarify the context, explain what you know, and write the sentences coherently. It is best to be lively and interesting.

I have the writing skills, the layout is good, and the article is written. A stud is as fierce as a tiger, reading only 55.

The problem came again, the content was not exposed. What to do, contribute!

However, the conversion rate of submissions is very low, less than 1%.

Later I learned that the official account is not just as simple as writing it, you need to learn to "operate".

The IT industry is busy with work, and they give up their rest time, write articles on weekends, and use all the rest time to input learning and output articles.

I really understand what is called originality is not easy. When the article is written and pushed out, am expecting readers to gain something. I look forward to 16100a5146a389 readers to like and share. This is the greatest encouragement to .

Writing learning

Since typesetting and writing skills are not good, start with learning writing.

A good article is very simple. It is to explain what it is actually talking about, extract the technical points I want to share, and use the mind map to write the main body and extract the subtitle, and list the just about .

Then enrich the content of each outline. In the process of writing, there must be a distinction between primary and secondary. Do not jump between primary and secondary. You should adopt a progressive and coherent writing content layer by layer. When writing each paragraph, ask yourself the following Questions:

1. What is it?
2. what to do?
3. What result

The following is a mind map of my writing skills:

To write an article, in addition to technical skills, you also need to consider the rigor of the logic, whether the writing is smooth, and the level must be clear.

These have nothing to do with technology. Some people do not necessarily write well in technical articles. Writing is an art.

In addition, I don't want to be too interesting, unless the audience of the article is noob. Believe me, if you want to really understand a point of knowledge, it must be difficult, and you need to think and practice more by yourself.

Contribution

After writing the article, I thought that as long as the content was good, it would get exposure and attention.

is just ridiculous.

The reality is cruel. After the article is written, it will not be exposed. It is a violent thing. During the writing process, I met many writers and realized that it needed to be operated.

submit to the organization's large-scale contribution, using the "16100a5146a593 high-quality content + large-scale contribution " method, to obtain the early seed fans.

Only oneself knows the hardships of this process. The tuba needs to be reposted to maintain the update frequency, and reposted articles are used to prevent fans from taking the pass due to frequent advertisements.

However, the conversion rate of reposting to get fans is extremely low, and about 100 readers will pay attention to the original author.

However, if you don’t submit a manuscript, you won’t get exposure to high-quality articles, and you won’t pay attention if you don’t read it, and you will fall into an endless loop...

Reprinting by others is also a kind of help to myself, at least it gets a certain amount of exposure.

Some readers actually don’t care who the original author is, and where to read the article is not to read it, whether you are the original or reprinted...

Even if there are high-quality articles, if there is no reasonable operation, they will be drowned in the news...

Thanks readers

There are so many public accounts in the vast sea of people, and some people choose to come to me. Life is really curious.

Thank you readers and friends for your attention, and thank us for knowing each other and growing up together.

This public account is a place where I can share programming experience, technical knowledge and grow up with readers. I hope I can go through the 5th year, the 10th year, or even longer...

I hope "Code Ge Byte" is a technical number with temperature.

What does temperature mean is not cold knowledge. I usually have time to explain technical issues to readers. Our lives are not only about technology, but more importantly, the methods of cognition, being a person, doing things, and some soft skills.

Knowledge is cold, it is like this, it is not like this, it is not like this, and some general knowledge and experience are hot and alive, and new things can be extracted through these repeated thinking.

In the era when the official account bonus has passed, there are also some newcomers who stand out and really admire them.

Good works need the support of readers. When we see an article that has gained something for ourselves, I hope everyone can support it.

In fact, the support method is very simple:

1. Give star articles are arranged out of order, no longer based on the timeline, and you may always miss the push of an official account without a star.
2. Like , if you feel that setting a star is bothering you, like an article you like, WeChat will record your preferences, and my article will be ranked in front of your timeline next time.
3. picks the wrong , which is to discuss the technical points of the article together and grow together.

In this way, more excellent content will be exposed, and the author will get positive feedback. Only then will there be more power to output high-quality content and feedback to readers.

Future plan

Continue to maintain the output of "high-quality content", still dominated by hard core.

• Continue to update Redis
• Spring series
• Design Patterns
• distributed
• MySQL
• Code Ge programming skills

When the next time you break xx million, you will get something different and move forward together.