The boss says software engineers should have a habit of writing

in the school, there are "arts students" and "Science students," the distinction between learning content, the way of thinking is also different. I am a science student, my major in university is computer science, after graduation, my work is an engineer . In this process, I found that the gap between liberal arts and sciences has never been bridged. Many of the engineers I met were afraid to write articles, and the liberal arts students had headaches when they saw the code.

I think , Programmers should develop the habit of writing. Because writing articles exercises many skills that are very useful for programming.

What's at the heart of writing and writing code is that they all need the ability to think clearly. Top software engineers are often good writers, and their articles and code are as logical, fluent and elegant.

There are many similarities between the article and the code: both start with a blank page, turn an idea into a complete product, and push to a specific audience; writing articles and writing code requires you to encapsulate a series of logical statements into modules that can be functions or paragraphs of articles. Good code should be as concise as a good article, or it would waste CPU resources or people's energy.

When a product is nearing completion, the software engineer will be as anxious as the writer's soon-to-be-published writing. Like writing articles, when software is never completely completed, engineers need to spend more time optimizing the code, developing new features, or re-doing a part because they worry that the published work does not show the best of itself.

software engineers should write because developing collaboration is becoming more and more important now. Open source projects can be attended by people from all over the world. Developing and operating a product often requires a large number of engineers. Whether it is the education of the School of the study of the analysis , or technical documents need clear and accurate text. Good writing skills facilitate communication between people and make the project run better.

You may think that some projects do not need to communicate, but writing about the software often facilitates learning and further discussion. Now, we no longer need to learn through the RFC documentation or technical manuals because there are tutorials written by other engineers on the web. In addition, we are able to learn a lot from comments, tweets and various blogs.

Software engineers need to write because they may enjoy the process of writing. Many software engineers expect the software they develop to "have an impact" and bring about changes in people's lives. In fact, by writing articles, you can also "have an impact" on people, for example, a blog post on management can help others motivate their team, teaching programming content may arouse a student's interest in computer science, and articles on career planning can help graduates find new career directions.

Even if no one is reading your essay, the process of writing is also useful and harmless. It helps you to clear your mind, to identify a problem, to strengthen or weaken some of your ideas. It is valuable to bring messy ideas together into streamlined text.

anyway , if you want to improve the development of software will go to the Ding school such a large site choose to learn and exchange, I hope my article on it friends are helpful.

The boss says software engineers should have a habit of writing