Why should software engineers develop the 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, my job after graduation is software 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 (Google Maps has 1100 full-time employees!). ）。 Whether it's GitHub reviews, code comments, or technical documents, you need clear, 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 hacker News commentary, Twitter and various blogs. Mention the blog, two more sentences. A good writing takes time. The words we wrote at the beginning may not be very good, then we need to spend some more time, modify them several times, and polish them. If you think you're too busy to write a blog, don't know what to write, or worry about your opinion being publicly documented, you should spend some time reading Steve Yegge's "You Should be blogging" (you should write Blogs) article. Even if the ideas don't convince you, I'm sure you'll get something after reading. Software engineers need to write because they may enjoy the process of writing. Many software engineers areExpect the software you develop to "have an impact" and bring change to 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. In short, writing helps to improve the level of software development, but also easier to collaborate in the development process, even for a science student, is also a very worthwhile thing to do. Free to receive the lamp brother even original PHP video tutorial CD/"Detailed PHP" Essentials Edition, details of the website customer service: http://www.lampbrother.net You can subscribe to the mail, I will occasionally share it-related tutorials and books. http://list.qq.com/cgi-bin/qf_invite?id=ea7d919ad263169bce2be53a3e16da0f0ec55ac36513c68e

