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/3 of the time for writing documents, and 1/3 of the time for programming; what ISO, CMM, and standards should be followed for writing documents; what is not written according to these standards is not a document, it is not a good document; what is not paid attention to documents is not formal. When asked what documents he has written and what standards he has written, this kind of person is speechless.

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

Programmers generally do not want to write documents, but programmers prefer to read others' documents. Even if you write a document, programmers generally do not write all the functions into the document, but complain that some of the functions in other documents are not described. Even if you are willing to write a document, programmers generally do not write the document in great detail, but complain that the documents written by others are 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 for this. I have summarized 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, the more. When thinking of writing so many documents, the programmer's head is too big.
2) document writing requirements are not low. There are format requirements and content requirements, you also need to draw a variety of flowcharts, relationship charts, interface diagrams and fill in a variety of table instructions, as well as to collect a variety of information. Although there is no technical content, it takes more time than programming, and it cannot be written.
3) in a regular Development Company, a series of change documents are usually required for a change. Only the final change document is the most important for constant changes. When weDon't knowWhen the current document is not the last one, we do not want to write documents that may be replaced by the following documents.
4) after a document is written, people who use the document are constantly asking for details. These questions are often broken down. This is because it is difficult to write documents that make everyone unable to raise any questions.

2. No time
In many cases, programmers are in a "time-tight, task-heavy" state. Driven by the rush to get programming results, programmers can't wait a minute for a change in programming. How can they think and have time to write the document and program it first? Even if they have the idea of first compiling the program and then completing the document, once they have completed a program, they will immediately jump to the second program. 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 drop you down and immediately move out of the document. Which of the following statements is important? The document is indispensable. I dare not say "I think documents are important ". This in turn illustrates the usefulness of the document for different people. For programmers, you only need to compile the program. Many programmers compile programs without writing documents. In their ideas, they should not write documents. 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, and changing requirements and Code make documents as obsolete as paper.
In reality, some documents have become a summary after project development, which does not work for the Development itself. It only retains an existing form 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 difficult to control document updates and system consistency.

4. No benefit
Since Programmers think that programming is the right way, it is an extra and auxiliary work for programmers to write documents. After doing so, there is no benefit for programmers.
Of course, the benefits of the document are more reflected in software companies, units, software users, and subsequent programmers. It is a good thing that "people planted trees, and people could ride the cold. Therefore, programmers are reluctant to write documents.
How important is the document? Some people raise it to the height of "copying the programmer's mind". Some people even say 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. So, will smart programmers clearly write documents?

5. Do not write
From the perspective of writing itself, writing a document is not easy. Documents have the document format and writing requirements. Nowadays, people only like to talk about things. Not many people write in writing at ordinary times, let alone write articles. Therefore, in theory, writing documents also requires learning and training, and requires accumulation of writing at ordinary times. When a programmer is asked to write a document, he will often answer you: "How to write? I won't ." If you don't write it, you don't blame you. If you don't learn it, you just say no, it's your fault. Are all those who write documents "Dummies? Do they not understand the principle of hard work?
When a man shows his love to a girl that he like and needs to use a love letter to confess, doesn't he write a love letter? Even if he does not write, he will surely 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 you afraid you won't write? These fears are all excuses. A really good programmer should not only be a programming master, but also a document writing master.
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 writing documents, they must improve their awareness and realm, or reward programmers who write documents. However, relying on systems and management allows programmers to write documents is only a professional drawback. One day, writing documents has become a professional job. When programmers and document personnel are separated, the programmers will read the document and write code with one mind, and the document staff will take this as their profession, 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 or management standards already have such a division of labor. However, IT departments in many small and medium-sized software companies or enterprises have not yet become professional. Programmers do not like to write documents, which may mean 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 should be able to leave in front of various problems in the document. It can be said that programmers who neither write documents nor appreciate documents are not qualified to say "I don't like writing documents.