Issue 13 · Nov 2–8, 2026Editions · Glossary · Archive · Method · RSS · HU / ENG

News of the AI era, curated weekly

Glossary › Developer basics

documentation

basicwidespread

Documentation is a written description that accompanies a piece of software: it explains what the program is for, how to use it, and how it is built internally.

In plain terms

Documentation is both the software's user manual and its blueprint. Like a washing machine's instruction booklet combined with a house's architectural plan: one shows which button to press, the other reveals where the wires run inside the walls.

It is prepared for several types of readers. The user looks for how to achieve what they want; the developer for how to connect the program with another; the operator for what to do if something breaks.

In the AI era, there is a new reader: the machine. A coding agent gathers information from descriptions just like a new colleague, so guides specifically designed for agents are now being created, explaining a project's rules and how to work within them.

What distinguishes it from the program itself: the code records what the machine does, while the documentation explains why and how it should be used. A good program can be unusable if no one knows how to handle it.

How it works

  1. The creators describe what the software is for and how to launch it; this is usually a short introductory file, the README.
  2. This is accompanied by materials for various purposes: step-by-step tutorials, task-solving guides, precise references on features, and background explanations on decisions.
  3. The description is often stored alongside the code, versioned in the same way, making it traceable which text belongs to which program version.
  4. Part of the reference is generated by programs from comments written in the code, while the text is increasingly drafted with AI assistance, requiring human review.
  5. While working, an AI agent reads descriptions and decides which tool to use and how based on them; if the description is inaccurate, the agent can easily make mistakes.

An everyday example

A new invoicing program has been introduced at your workplace, and you can't find how to cancel an invoice. You open the help pages or ask the program's built-in AI assistant; ideally, either way, the answer draws on the documentation. If the documentation is outdated, it will send you to the wrong button.

Who is affected

developerIt reads and writes it daily, and a coding agent works on the project only as well as the descriptions are precise. → Code
employeeThe help sections, knowledge bases and internal process descriptions of workplace software are all documentation; this is how you learn new tools. → Work & HR
entrepreneur, executiveIf a company's systems operate only in the minds of one or two people, their departure means the knowledge is lost, and AI tools have nothing to rely on.
lawyer, citizenThe EU AI Act requires technical documentation for both high-risk AI systems and general-purpose AI models, which is the basis for verifiability. → Law

A common misconception

MythDocumentation is unnecessary paperwork; good code speaks for itself, and if needed, AI can write it anyway.
In realityFrom the code, you can see what the program does, but not why it was made that way or what it was intended for. AI quickly writes fluent descriptions, but does not know the intent, and if you do not check it, it may include confidently sounding errors.

Limits and risks

Similar, but not the same

Related concepts

Broader

software development, knowledge management

Narrower

README, API documentation, user manual, technical documentation

On the edge

code repository, version control, API, coding agent, kontextus

A brief history

Software documentation is as old as programming: printed manuals were provided for computers from the start. With the spread of the internet, descriptions moved to the web, and since the emergence of large language models, they are also prepared for machine readers.

Where things stand

At the end of 2026, documentation is a self-evident part of software development, and it is changing in two directions: an increasing share is written with the help of AI, and more and more is created specifically for agents. Its quality strongly influences how reliably agents work.

Status: 2026 November

In the news

Appears in 17 Agent Age stories; the curve shows weekly occurrence in the news magazine.

Also known as

documentation · documentation · docs · doksi · software documentation · software documentation · technical documentation · technical documentation

Sources

This entry was machine-edited and has undergone machine expert review; the “In the news” section updates automatically from Agent Age stories.