Good technical writing begins by assuming the reader is busy and intelligent. The article should answer a real question without making the reader dig for the point. That means starting with the problem, naming the concepts clearly, and avoiding the habit of delaying the useful statement until the final paragraph.
A strong piece of writing uses examples to clarify rather than to decorate. Definitions, comparisons, and concrete situations help a reader hold the idea in memory long enough to understand it. The writer should also keep the prose modest: one claim at a time, one paragraph at a time, one step in the argument at a time.
Editing is where the work becomes visible. The first draft captures the direction of the argument, but the second and third passes decide whether the argument is actually understandable. Sentences that repeat themselves, transitions that over-explain, and unnecessary adjectives can usually be removed without harming the meaning. In fact, the meaning usually becomes stronger when the excess is stripped away.
The best technical article leaves the reader with an improved mental model, not just a collection of facts. If the reader can explain the idea to someone else afterward, the writing did its job. That standard is demanding, but it is also the most reliable measure of whether the article deserved to be published.