How to Master Writing Technical Articles: Proven Strategies for Impactful Content

For a science student who never liked Chinese, reading, or writing, I never imagined I would one day write an article teaching others how to write articles :)

Why Write Articles?

Understanding something does not guarantee you can articulate it; being able to articulate does not guarantee you can write it. This is the essence of the “Feynman Technique.” Writing forces you to deepen your understanding, clarify your thoughts, and build a personal knowledge system, which is the best way to learn and improve.

Beyond personal growth, writing also expands your influence. Over the past four years I have systematically built my knowledge system through reading, note‑taking, writing, and sharing. I have won “Best Author of the Year” three times, published many headline articles, and contributed around ten pieces to Alibaba’s technical public account, with several articles exceeding 30,000 reads.

These experiences led to a book published by People’s Posts and Telecommunications Press, “The Path to Code Mastery: From Coder to Craftsman,” which earned me the IT‑category Best Author award.

What Makes a Good Technical Article?

A common benchmark is that a good article has a complete framework, deep and clear thinking, and at least 80% original technical content. While metrics like views, likes, comments, and collections can be useful references, the ultimate judgment remains subjective.

In my view, a good technical article should satisfy two core conditions:

It conveys valuable information.

Its structure and logic are clear, making it readable and understandable.

Bonus points go to articles with literary flair and humor.

How to Write a Good Technical Article

Content usefulness

The most important thing is that readers feel they have gained something. Even a short piece that explains a “small thing” clearly can be excellent. For example, my article “Alibaba Acronyms and Terminology Guide” simply listed all abbreviations I encountered at Alibaba, yet it became my most popular piece with nearly 100 K reads and 3 K likes.

People are curious about the full forms and origins of abbreviations, which gave the article its value. Similar information‑integration articles include introductions to cloud‑native technologies, comprehensive front‑end technology overviews, newcomer handbooks, and speech collections.

Articles that present personal technical insights and honest opinions also resonate strongly with readers.

Structure Clarity

Good content needs a good structure, just like a dish needs balanced color, aroma, and taste. I recommend the “Pyramid Principle” for building clear structures: start with a central thesis (usually the title), support it with multiple arguments, and further break down those arguments as needed, creating a logical, top‑down hierarchy.

Using this approach makes the article’s logic evident and the structure tight.

For technical articles, the 3W2H model is helpful:

What: What is abstraction?

Why: Why is abstraction important?

How: How to perform abstraction?

Where: Where can abstraction be applied?

How much: To what extent should abstraction be applied?

I applied this model while drafting the current article, as illustrated below:

Deliberate Practice

Writing is a skill that can be learned through practice. Like the concept of “deliberate practice,” simply repeating is not enough; you must set progressively higher goals to achieve continuous improvement.

For instance, after becoming comfortable with writing, I now focus on making my articles more engaging. Techniques such as opening with a striking statement—e.g., “We all die; we are lucky…”—create conflict and suspense that naturally draw readers in.

Iterative Optimization

Writing shares many similarities with coding. Both require clear structure, and great systems are often iterated rather than designed perfectly from the start. I repeatedly revise my articles—re‑organizing sections, adding or removing information, and tweaking wording—until I am satisfied.

The current article itself went through several drafts; the first version was scattered and lacked clear structure. By treating the article as a sample of how to write, I iterated until it became coherent.

The key is to start writing without fear of imperfection; the process itself will lead to improvement.