Technical discussion should be concise and clear

I often post a reply to the debate in various technical forums and find that the current technical staff ArticleThere is a trend-smelly, long, and unorganized. Such replies often make people confused. What's more, there is nothing to say.
When there is more, there must be something wrong. Some people will find these ideas later, and all the replies will go beyond 108,000.

Technical posts or replies should be simple and clear. Put forward your own ideas, and then list the basis for supporting this idea. It is better to give an easy-to-understand example. Disagree with others' ideas.
Agree to what, and then raise your own arguments. These are the argumentative papers I have learned in primary school. However, I can see that the mixed technical staff on the Forum are either illiterate and semi-illiterate with unsatisfactory words, or just a thousand words.
Author or critical author. My reply on the Technical Forum is generally as concise as possible. It is enough to explain the problem. however, the disadvantage of this method is that it is not perfect, so it is easy to ignore the context and only pay attention to the language table.
The man in question refuted.

Therefore, we may wish to learn official articles. We 'd better have a 1234 discussion, with each point starting with a comprehensive sentence.

Digress: technical books

Speaking of this question, I think of the publishing of technical books in China and abroad. The style of foreign masters (unfortunately, computer masters are generally foreigners) is simple and practical, as long as you can clarify the problem, the simpler the better. Image
Design patterns, the essence of UML, the effective use case patterns, and other books about ideas are thin books that are worth your taste over and over again, while books written by Chinese people, as if not thick, it cannot be called a book,
1024 pages of Java and patterns are a real secret. The reason is that I think of the preface to a book written by a foreigner (which one I forgot) I read in the previous section. It is said that after the writing, it took a while to get closer.
Half of the content is reduced, and there is a gap between the content that readers can easily find (such as basic knowledge) and the core content to be discussed in the book, I think it is not suitable to cut down all the content in this book. In contrast, domestic
Technical books, also a few days ago, I bought a book to write an industry's information system. There are more than 300 pages, and only 60 pages are related to the industry. Other parts can be called introduction to computer science. even layer-7 Internet protocols are included
. I think the author wrote an outline before writing a book, and then copied the content to it. As long as the content is reached, no one wants his book to be a big part, and the number of pages should go up.