# Automatisierung

The automation designed based on a few specific principles:

* It should follow the same methodology as the human team members.
* It should use the same tools as the human team members.
* If another team member was doing administrative work on a machine or cluster (group of machines), the automation would step out of the way if asked, just like a human team member would.
* Like a good team member, if it got confused it would back off and ask other members of the team for help.

[Automation Should Be Like Iron Man, Not Ultron](https://queue.acm.org/detail.cfm?id=2841313)

## Links

* [Creating Processes and Automating Everything](https://seanwes.com/podcast/499-build-a-profitable-agency-part-4-creating-processes-and-automating-everything/)
* [Do-nothing scripting](https://blog.danslimmon.com/2019/07/15/do-nothing-scripting-the-key-to-gradual-automation/) - Schritte in Programm schreiben und auf Feedback warten
* [Wanted: High Performers for the Last Job You’ll Ever Have](https://every.to/chain-of-thought/wanted-high-performers-for-the-last-job-you-ll-ever-have)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://notes.d15r.de/produktivitaet/automatisierung.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.