Why are programmers reluctant to write documents?

 

When talking about documents, someone will talk to you about how foreign companies, large companies, and formal companies attach importance to documents.2/3Time is used to write documents,1/3Time used for editingProgram; What do I need to write a document?ISO, WhatCMMWhat are the standards? What are written according to these standards is not a document or a good document. Documents are not formal. When asked what documents he has written and what standards he has written, this kind of person is speechless. Such a person is a media advertisement.

In any case, documents are the biggest weakness of programmers. Some programmers who are known as masters are often inferior in terms of documents. No matter whether the programmer is in a large company or a small company, whether the program is writing documents or not, most programmers are reluctant to write documents in their hearts.

There are so many strange things in the world that sometimes people cannot understand. Programmers generally do not want to write documents, but programmers prefer to read others' documents. Even if a document is written, programmers generally do not write all the functions into the document, but complain that the functions of other documents are not described. Even if a programmer writes a document, the programmer generally does not want to write the document in detail, but complains that the document written by others is not detailed enough. The document is definitely a contradiction in front of programmers. If programmers prefer to write documents or read documents, I guess most programmers will choose the latter.

Why are programmers reluctant to write documents? There are many reasons. I may wish to summarize the following points:

 

1,Be bored

From the very beginning, programmers have buried a program seed in their hearts. They think that programmers are programming, computers, and programmers. Whether writing documents before programming or after programming. They all think that writing documents is annoying.

1)There are too many types of documents. The more formal it is. The idea of writing so many documents is too big for programmers.

2)Document Writing requirements are not low. There are format requirements, content requirements, also need to draw a variety of flowcharts, relationship charts, interface diagrams, also need to fill in a variety of forms, to collect a variety of information. Although there is no technical content, it takes more time than programming, and it cannot be written.

3)Generally, a formal development company needs to write a series of change documents for a change. When changes continue,Only the final change document is the most important. When we do not know whether it is the last document, we may not be willing to write the document that will be replaced later.

4)After you write a document, people who use the document constantly ask this question. These questions will often cause you to crash. It is difficult for you to write documents that make everyone unable to raise any questions.

 

2,Not available

In many cases, programmers are in a "time-tight, task-heavy" state. Driven by the rush to see the results of programming, programmers can't wait a minute for a change. How can I write the document before programming. Even if they want to compile the program and then rewrite the idea of the document, once a segment program is completed, they will immediately jump to the second segment. In this case, you can only write documents later in the project development stage. If you write a document, the time for writing the document is long before the programming time is exhausted.

 

3,Useless

The importance of a document is actually different for different objects. If you say that the document is useless, someone will immediately drown you with foam. They will immediately move out of the document, which is important and indispensable. I dare not say "I think documents are important ." This in turn shows that the usefulness of the document is different. For programmers, it only needs to compile the program. Many programmers compile programs without writing documents, and do not write them in their ideas. If you compile programs by document, ensure that the document is correct and cannot be modified. In fact, documents are not as fast as programming, programming is not as fast as changing, changing needs andCodeMake the document look like an outdated piece of paper.

In reality, some documents have become a summary after project development, which does not work for the Development itself. It only retains some forms to meet the needs of various specifications. In this case, the document has no practical value, so it does not work even if the programmer writes it. Especially after the project is put into operation, after several upgrades, the initial documents have long been unable to match the actual situation, and it is even more difficult to update the documents and ensure system consistency.

 

4,No benefit

Since Programmers think that programming is the right way, it is an additional and auxiliary job for programmers to write documents. After doing so, it will not be of any benefit to programmers. So few people are willing to do anything that has no benefit.

Of course, the benefits of the document are more reflected in software companies, units, software users, and subsequent programmers. It is a kind of cool thing for people who have planted trees.However, there are too few people doing well now. Therefore, programmers are reluctant to write documents.

How important is a document? Someone raised it to the height of "copying the programmer's mind.Some people even said that when programmers leave, as long as there is a document, the software company can recruit new people and the company will continue to work. In this case, smart programmers will clearly write the documents and wait for the company to get rid of them? Programmers write the documents unless the company pays for them.

 

5,Not Write

From the perspective of writing itself, writing a document is not easy. The document has the document format and the document has the writing requirements. Nowadays, the ability of people to speak is huge. Many people usually write with a pen, not to mention writing.Article. Therefore, in theory, writing documents also requires learning and training, which requires accumulation of writing at ordinary times. When you ask him to write a document, he will often answer you: "How to write? I won't ." In today's society, there is a strange phenomenon that people do not think of what they do, rather as an honor. You don't want to write, but you don't blame you. If you don't want to learn, you just say it's not yours. Is it true that all the people who write the document are dummies? Do they not understand the principle of hard work? Therefore, do not expose ignorance to others. You must first master the required skills. Do not wait for the time to say no.

 

When a man falls in love with a girl he likes and needs to use a love letter to express his confession, doesn't he write a love letter? Even if he won't write it, he will certainly overcome the difficulties and write his love letter. This is his subjective nature. How can programmers get bored if they want to write documents subjectively? How can I be afraid of being empty? Why are documents useless? Why are there no benefits? Why are you afraid you won't write? These fears are all excuses. A really good programmer should not only be a programming guru, but also a document writer.

 

The reason why programmers really do not like writing documents is that the documents are for others rather than for themselves.To make programmers like to write documents, they should improve their awareness and realm of "serving the people", or reward programmers who write documents in RMB. Relying on the system and management, programmers can only write documents as a profession. One day, when writing documents becomes a professional job, when programmers and document personnel are separated, programmers will read the documents and write code with one mind, document workers will take this as their profession and write documents with one mind to get the salary. We will not discuss it any more. This division of labor must be a trend in the future. Some large companies and management companies have such a division of labor. Only a lot of small and medium software companies or enterprisesItThe Department has not yet become professional. programmers do not like to write documents to demonstrate that they are unwilling to assume too many roles.

 

In any case, as a programmer (especially a good programmer), you must learn to write documents and appreciate documents. Whether you like it or not, you can leave the document in front of various problems. I can say that programmers who neither write documents nor appreciate documents are not qualified to say "I don't like writing documents.

 

 

Blog Source:Http://www.cnblogs.com/n216/archive/2010/06/24/1764061.html