Software engineers should write more articles

In primary schools, there are so-called math children and Chinese children. By the way, when you were young, were you assigned to a certain camp based on your academic performance?

I used to be a math kid, so I enrolled in computer science and decided to become a software engineer. However, in this process, the title of math children and English children has not disappeared, and this gap has even become more obvious. Therefore, today's engineers are generally afraid of writing articles. And those writers who can write articles often get confused immediately when they see the code.

What a pity! Yes, software engineers should be able to write code, but they should also write some articles.

The reason why software engineers should also write articles is because writing can promote many skills that are also needed in programming;The core skills are the ability to think clearly. The best software engineers are also great writers because their prose is as logical, elegant and clean as their code.

Code and articles have a lot in common. It's all blank at the beginning, and then I write it out bit by bit according to my own ideas, and finally an independent product comes out. Products are made up of a series of logical statements bundled into modular units - whether they are software functions or article paragraphs. Good code is like beautiful writing, concise, clear and expressive. And poor code is a waste of CPU cycles, just like a messy article is a pure waste of mental resources. Generally speaking, the outline of the article is the architecture of the software.

Engineers feel just as restless as writers as deadlines get closer. Just like articles can always be improved, we can never say that our software is complete. This also makes engineers need more time to add functions and reconstruct modules. Engineers often need to worry that they are not doing their best.

The reason software engineers should try to write is because our current projects increasingly require collaboration. Open source projects invite participation from people around the world, and product development requires the collaboration of many engineers. (For example, Google Maps has 1100 full-time employees!) Good written communication skills, whether it’s writing GitHub comments, code reviews, or writing technical documentation and communicating clearly and concisely can contribute to the forward development of projects like these.

Even for projects that do not require communication, writing something can often promote learning and discussion. You should know that thanks to tutorials written by other engineers, we don't have to study those daunting RFC specifications and technical manuals. Articles about technical discussions can only be published on "Hacker News" and tweet if they are particularly well written, and the rest will be directed to blog articles.

Besides, writing this blog post also requires an investment of time. Just as good articles take time to write, starting with a first draft and then improving the quality through multiple revisions.

Software engineers should write articles because they might actually enjoy writing. In the past, we were constantly indoctrinated with the idea that we are good in this field of liberal arts, so most of us may never have thought that we might also have the potential to write. Will this make you suddenly full of interest and motivation?

Also, writing can have a huge positive impact on your career plans. Management blog posts can help managers inspire their teams, and programming tutorials can ignite students’ interest in computer science. Spark. Some career advice articles can even inspire graduates to embark on a new career path

It doesn’t matter, the writing process can benefit you a lot. It can train your ability to clearly explain a certain topic, and the process of turning some disorganized ideas in your mind into concrete words step by step is also very valuable.

Writing will also affect engineers' passion for writing software, which is as useful as it is. Combine your software skills, work together, and you'll suddenly find that writing has become a very valuable activity even for those so-called math kids.

Writing provides the same. The impact of feeling inspires engineers to write software. Combined with this how to facilitate collaboration in software engineering, writing suddenly seems like a worthwhile activity LAMPBand of Brothers.

Original

Video tutorialCD /"DetailsPHP" Essential version, please contact the official website customer service for details: http: //www.lampbrother.net

PHPCMSSecondary developmenthttp://yun.itxdl.cn/online/phpcms/index.php?u=5

WeChat developmenthttp://yun. itxdl.cn/online/weixin/index.php?u=5

Mobile Internet server-side developmenthttp://yun.itxdl.cn/online/server/index.php?u= 5

JavascriptCoursehttp://yun.itxdl.cn/online/js/index.php?u=5

CTOTraining Camp http://yun.itxdl.cn/online/cto/index.php?u=5

The above has introduced that software engineers should write more articles, including aspects of content. I hope it will be helpful to friends who are interested in PHP tutorials.