Guiding AI writing to make technical text easier to review

a11.to

The problem is that a lot of people who use agents to code nowadays, or Vibe coders, did not start from traditional engineering organizations, so they have no idea what best practices are in DevOps. Personally, I have a rule in every one of my tickets to update documentation when done. Ever so often, I would ask an agent to audit all the changes that have happened since the last audit, compare with the technical documentation and update whatever is stale. And occasionally, I would just have an agent do a pass and tighten the language, remove redundancies, and fine-tune it for human reading or agent reading.

Yeah, this is true—insufficient engineering experience to even recognise these issues is part of the problem. +1 to "fine-tuning" specifically the language or a workflow, too. I did it in the article and many people around are doing the same, apparently.

But still, in my experience, even in places with good engineering expertise and culture, there is also pressure to ship really fast, so systematic approaches to these things get overlooked, and gradual slopification happens. No perfect answer as to what to do with this, but I think it's important to name the problem and offer at least some easy solutions.

True, that's exactly how startups are, even before AI. It's not until they start getting big that they realize that they need to invest some time and create some processes to help them save time in the future

Reply on news.ycombinator.com