BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//pretalx.com//pycon-sweden-2026//talk//VAHREY
BEGIN:VTIMEZONE
TZID:Europe/Stockholm
BEGIN:STANDARD
DTSTART:20251119T000000
TZNAME:CET
TZOFFSETFROM:+0100
TZOFFSETTO:+0100
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20260329T030000
RDATE:20270328T030000
TZNAME:CEST
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
END:DAYLIGHT
BEGIN:STANDARD
DTSTART:20261025T030000
RDATE:20271031T030000
TZNAME:CET
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
SUMMARY:Why do we have to deploy to find out it's broken? - Marcus Kohlber
 g\, André Eriksson
DTSTART;TZID=Europe/Stockholm:20261119T154500
DTEND;TZID=Europe/Stockholm:20261119T161500
DTSTAMP:20261111T054226Z
UID:pretalx-pycon-sweden-2026-VAHREY@pretalx.com
DESCRIPTION:Python gives us a fast feedback loop: change some code\, run i
 t\, see what happens. But once our applications depend on databases\, queu
 es\, and other services\, that feedback loop gets much slower. Code can wo
 rk locally and still fail in production because of a configuration mistake
  or a mismatch between what the application expects and what’s deployed.
 \n\nWhat if we could catch those integration problems before deploying?\n
 \nIn this talk\, I’ll show how we’ve built an open source project that
  understands the infrastructure an application needs directly from its cod
 e. We’ll follow a change from local development to deployment\, look at 
 integration mistakes we can catch in seconds\, and unpack how it works und
 er the hood. You’ll leave with a different way to think about the bounda
 ry between application code and infrastructure\, and what happens when dev
 elopers and their AI coding agents can quickly get feedback on both\, inst
 ead of waiting for deployment to find out what’s wrong.
LOCATION:Auditorium
URL:https://pretalx.com/pycon-sweden-2026/talk/VAHREY/
END:VEVENT
END:VCALENDAR