# What happens after AI writes the code?

Canonical: https://brew.new/templates/gitlab/what-happens-after-ai-writes-the-code-3

Brand: gitlab.com
Category: event-invitation

![Preview of What happens after AI writes the code?](https://cdn.brew.new/email-preview-336adc98bb4366f2-tracking_r57r8h0a7gtnvs5y2a7cxrj2yh8hyj0b-1794327694477.png)

## Email content

Hi,

Hot repositories pin traffic to specific nodes. Agents make it worse by retrying, branching, and writing in parallel, so one busy repo can stall everyone on that node.

Join us live on November 17 for a 45-minute tech talk with Patrick Steinhardt, Technical Lead on GitLab's Git team and a core Git contributor, where he’ll walk through the fix at the storage layer: object storage holds the source of truth, and stateless nodes serve repositories on top of it.

Because the pluggable storage work landed upstream, this builds on Git itself, not a fork, benefiting the whole community.

You’ll walk away able to:

Lose a node without losing data. Recovery costs a cache warm-up, nothing more.

Serve consistent snapshots to readers without blocking writers.

Run parallel agent pushes against shared state with zero corruption.

Scale horizontally by adding nodes, with no re-architecture.

Register now

---

This email was sent to you@example.com.

Please visit the GitLab Email Subscription portal to update your preferences.

If you no longer wish to receive marketing emails from us, you may unsubscribe at any time.

[Open and remix this design](https://brew.new/templates/gitlab/what-happens-after-ai-writes-the-code-3)

[Browse email designs](https://brew.new/browse/templates)