Automation as a culture, not a gadget

When a team says "we automated everything", usually it turns out only one scenario is automated — and the rest is manual work.

Automation becomes a culture when it answers three questions: what do we do most often? where do we make mistakes most often? what takes the most time of the most experienced people?

Where to start

• start with one repetitive action and take it to completion;
• make changes verifiable and reversible;
• record what you automate — otherwise it is not documented.

These principles are at the core of YoDMIN: not a "script for the sake of a script", but a predictable process where the engineer has fewer chances to make a mistake.

Automation does not replace the engineer. It replaces their mistakes.