Writing Technical Articles examines how researchers can communicate technical contributions clearly, with particular attention to computer science, electrical engineering, systems, and networks. It distinguishes original research from survey papers and identifies four kinds of results: algorithms, system constructions, performance evaluations, and theories. Throughout, the emphasis falls on explaining what is new, why it matters, and how readers can assess its validity. The guide follows a paper from abstract and introduction through architecture, implementation, evaluation, related work, and conclusions. It recommends drafting the approach and results before the introduction, then writing the abstract and choosing the title. Contrasting introduction examples show how a specific problem and contribution provide stronger direction than vague claims about an expanding research field. Detailed advice addresses active sentences, strong verbs, consistent terminology, abbreviations, units, figure references, bibliography entries, and LaTeX presentation. Sections on simulations and experimental papers stress reporting parameters, uncertainty, comparison baselines, limitations, and enough software and data information to support replication. An account of conference reviewing explains how submissions move through reviewers, scores, and committee discussion. The final three pages change tone with How to Have Your Abstract Rejected, a satirical essay that recommends lateness, excessive length, missing motivation, obscure references, and confusing prose. Its deliberately inverted advice reinforces the practical guide’s central concern: making useful research understandable to its readers.