Operations log 05.2025 to 09.2026
Workshops for development teams that give their agent real access: to the repo, to the database, to the server. One day for what cost me more than a year and a series of unpleasant evenings.
Next date: Wednesday, 28 October 2026 in Berlin. Agents in Everyday Work, €290 net.
14.06.2026Application server
Incident
To check whether a variable was set, the agent opened the entire environment file. Database password, signing key, two cloud credentials and an admin token were in the transcript afterwards.
CostAll keys rotated, deploy freeze, half a day.
2Everything the agent reads leaves the machine
I only teach what I have run myself. That limits the subject but makes it hold up. The second list is expressly part of it.
This is what it is about
This is what it is not about
A date runs from four registrations. Until it is confirmed, your registration is non-binding and free. You will know at least ten days in advance whether the date goes ahead. The invoice comes only after that.
The whole road: prepare the repo, draw the lines, spot misbehaviour, roll out to the team.
At most 8 participants. Developers, tech leads and freelancers who already use a coding agent and now want to let it touch code that somebody is liable for.
€690 €890
net per person
12 Nov 2026Pilot
The solid start for teams a few weeks in who notice that it is not running smoothly.
At most 10 participants. Teams that have installed a coding agent and so far use it like a better autocomplete. Also suitable for product and ops people who need to have a say.
€290 €390
net per person
28 Oct 2026Pilot
Give the agent safe access to your data, via MCP, with approvals, an audit log and rollback.
At most 8 participants. Product teams with their own backend who want to give the agent access to their data without handing it the database.
€390 €490
net per person
25 Nov 2026Pilot
No second-hand course material. The content is the log of my own work, including the places where it went wrong. Before that lie twenty years of IT projects, today with responsibility for developer teams at several clients.
I build and run software for a few very different clients: a dating app with end-to-end encryption and specially protected data, LED perimeter advertising in stadiums from the embedded player to playout, several content platforms and my own room rental business. Add a home lab with local models on Mac minis and one graphics card.
Most of it was created through agents and is run through agents. Highly available Postgres, a load balancer pair with failover, a VPN backbone, encrypted disks unlocked over the network, central logs, a web application firewall, backups in three tiers down to cold storage. At the other end of the scale, embedded players with 40 MB of RAM and a custom anti-aliasing path in C, because the usual filters flicker when downscaling an 11,000 pixel wide template.
Along the way everything that can happen has happened. Credentials in the transcript. A firewall rule that took the production API off the network. A cache that halved a media library. A public bug report with my real address in it. Each of these incidents left a rule behind. Those rules are the core of the workshops.
I still use the tools every day and would not want to go back. This is about the distance between a demo that impresses and a workflow a team can rely on.
As of 15 September 2026. Counted from September 2025, it started in May.
Distilled from the corrections I wrote down over a year. Each one is there because an agent broke it. The long part of the one-day workshop goes through them with the incidents behind them.
The open dates run in my own workshop room in Berlin Prenzlauer Berg. The room has 4.5 square metres of whiteboard, a 75-inch screen, its own kitchen and a lounge for the breaks. It belongs to me, which is why the groups are small and the day is not run on a stopwatch.
Small groups
Eight to ten people, depending on the format. Everyone works on their own machine and their own repo. I come round to everyone.
Getting there
Grellstraße 37, 10409 Berlin. Greifswalder Straße S-Bahn station, four minutes on foot.
Catering
Coffee, tea and drinks are included. At lunch we go out to eat together, there are several good places around the corner. Breakfast on request for a surcharge.
The one-day workshop assumes exactly that. It starts at the point where you notice the agent beginning to find its own ways on bigger tasks. If you do not yet have a rules file in the repo, no command of your own and no list of what the agent never does alone, there is plenty to do.
The examples run on Claude Code because that is what I work with. The rules and failure patterns apply to any agent with tool access. In the hands-on part you can work with your own tool as long as it knows project files with rules and custom commands. Let me know beforehand and I will prepare for it.
No. All exercises run on your own repos, locally. For the part about production systems I use my own infrastructure. Nobody touches anyone else's systems.
Then you hear from me at least ten days in advance and there are no costs. Until the date is confirmed, the registration is non-binding. An invoice only goes out once the date is running.
Materials yes: the rule set, templates and the examples from the day as a repository you keep. Recordings no. In the groups people talk about real projects and that only works without a camera.
Yes. For whole teams in-house is usually the better choice, because then everyone sits at the same code and the day is tailored to your systems. Berlin at no extra charge, otherwise travel and possibly a night's accommodation are added.
Until then the registration is non-binding and free. You get an email from me as soon as it is clear whether the date runs. If you would rather have it in-house or a topic is missing, put it in the form.