I recently gave detailed feedback to an intern on our team who was writing Autoresearch for Data. That review inspired me to write down some tips and tricks I use for engaging technical writing in the age of coding agents.
Coding agents can rewrite paragraphs and rebuild interactive charts quickly. When an agent can produce several ways to explain a result, writing more is easy. The scarce work is editorial: deciding what deserves attention, how to show it, and what evidence the reader needs to trust it. The first decision is the order in which the reader encounters that evidence.
Lead with the strongest result
Reader attention is scarce. A long setup can lose people before they reach the main payoff, so put the main result up front. For example, our post leads with this summary:
"We gave an agent a budget of 11,000 H100 hours to find the best data mixture for training a 2B VLM."
