A SAP technical author’s creative experience in the Sibu community over the past few years | Written on the 9th anniversary of Sibu

I am an old programmer. In September 2000, I entered the University of Electronic Science and Technology of China to engage in undergraduate studies in computer science. I first came into contact with segmentation fault when I was studying C language programming in my sophomore year. At that time, I was a little novice in C language. Due to my unreliable grasp of the concept of pointers, I often encountered segmentation fault errors in the C programs I wrote. .

At the time, I would not have thought that after 18 years, I would continue to record the technical accumulation of my daily work as a developer in a technical community called segmentfault.

After graduating from graduate school in 2007, I joined a business management software company called SAP, and I have been working until now. SAP also has its own original technology for full-stack application development, but compared with the current front-end Angular, React, Vue troika, back-end Java, Node.js, and Go language technologies in the IT industry at home and abroad, the SAP technology ecosystem The circle is relatively closed, and the absolute number of practitioners is far smaller than other popular technologies. Because of these objective reasons, there are not too many excellent Chinese materials for popularizing SAP technology in China, especially articles that introduce the latest SAP technology and future technology development trends. Therefore, in recent years, with the increase of my working years in SAP and the accumulation of SAP technology applied, I have set myself a goal: to become an outstanding SAP technology writer in China.

I have been working for 14 years and have experienced many technical writing platforms, such as Zhihu, Jianshu, CSDN, IT Pub, Alibaba Cloud Community, Tencent Cloud Community, Blog Park, and of course Sifu Community.

The characteristics of the Sifu community are very prominent, and the impression given to me is very good.

First of all, whether it is the display style of the community content, or the editing interface of the technical article, it is very refreshing, without any ads. Technical writers can devote themselves to writing text without being distracted by irrelevant factors.

Secondly, the content quality of Sifu community articles is quite high. In some domestic technical communities, a certain number of articles have been complained by programmers about "Title Party", "relying on grandstanding to gain traffic". In the Sifu community, whether it is in the Q&A section or everyone’s article creation, the title and content are simple and unpretentious, closely tied to the technology itself, which firmly attracts many domestic developers who are willing to concentrate on technology research like me. Choose to create and answer peer questions in the community for a long time.

Although almost most of the articles I create are written with SAP technology, and the reading volume is not as high as that of the works of many outstanding creators in the community, I have indeed helped some domestic SAP technical practitioners and helped them/ They solved some practical problems encountered when doing SAP development. I also feel very gratified that my article can help others.

I am also fortunate to be the Top Writer of Sifu Community in 2019:

And received a postcard from the community CEO Gao Yang.

As a programmer, I am infinitely grateful and admire for Mr. Gao's single-handed creation of such an excellent technical community, which has benefited thousands of programmers in the country.

Although I cannot be as successful as Mr. Gao, I can continue to output technical articles on the Sifu community to help developers who work in the same technical field as me.

The road is long and long, and I will continue to search up and down. I wish the Sifu community better and better.

This article has participated in the SegmentFault essay "9th Anniversary of Thinking", and you are welcome to join in.