> We have the luxury of precision, where most often one term means one concept or thing. A 1:1 mapping with little ambiguity. Deviating from that is almost always the wrong decision.
This is true of some words in a piece of technical writing, but not most of them. Don't allow yourself to be fooled into thinking that every word in your paper has a single clear meaning. At the same time, you're right that a writer shouldn't reach too far to find synonyms just to mix things up.
> Short, concise, to-the-point sentences. Sparing use of filler words (thus, however, ...).
"Thus" and "however" are not just filler words! Yes, they may be overused. But they also signal the conceptual relationship between one thought and the one that follows it in a clear way, at the beginning of the sentence. This allows the reader to understand how a sentence relates to the previous one before they have fully parsed and understood it.
Yet, technical writing doesn't work that way. Synonyms are almost always wrong. We have the luxury of precision, where most often one term means one concept or thing. A 1:1 mapping with little ambiguity. Deviating from that is almost always the wrong decision.
Also notice the style I am writing this comment in. Short, concise, to-the-point sentences. Sparing use of filler words (thus, however, ...). I wish all technical writing was more like that (and I find that good technical writing either is, or is on such a high level that they can get away with longer sentences). I believe it a boon: you get a style of "Statement. Statement. Idea. Question. Idea. Statement. Solution. Conclusion.", if that makes sense, allowing easier mental access and partitioning. Technical topics are hard, and writing should accommodate the reader, making it as easy as possible.