I always think that the document is really important for the project and the team and should be written regularly and in detail . It can do everything in parallel without asking experienced programmers here and there. But in fact, I find that many developers (even leaders) do not pay so much attention to documents and just take them for granted, which makes me feel bad.
So is my attitude to documents correct? Are documents really important? How should I convince the team leader to pay more attention to the documents?
If the documents are important, the second question arises. Who should write the documents? IMO, they should be written by experienced programmers, such as the creator of the framework (if we use our own infrastructure), important parts of the project (for example, the db scheme, the whole architecture, etc.), etc.
The benefits are obvious, for example, help fresh people, help support, and more.
So, in my opinion, experienced programmers (the definition may be different here) should pay more attention to writing documents than writing code after the infrastructure is completed.
Am I saying it right?
Thanks for sharing these questions.
source
share