BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//pretalx.northbaypython.org//nbpy-2026//R7VNEX
BEGIN:VTIMEZONE
TZID:PST
BEGIN:STANDARD
DTSTART:20001029T030000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10;UNTIL=20061029T100000Z
TZNAME:PST
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
END:STANDARD
BEGIN:STANDARD
DTSTART:20071104T030000
RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=11
TZNAME:PST
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20000402T030000
RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=4;UNTIL=20060402T110000Z
TZNAME:PDT
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
END:DAYLIGHT
BEGIN:DAYLIGHT
DTSTART:20070311T030000
RRULE:FREQ=YEARLY;BYDAY=2SU;BYMONTH=3
TZNAME:PDT
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:pretalx-nbpy-2026-QVQEP3@pretalx.northbaypython.org
DTSTART;TZID=PST:20260426T105000
DTEND;TZID=PST:20260426T111500
DESCRIPTION:Errors. They happen. Sometimes we wish they wouldn't but they d
 o and the code we write and the systems we build have to handle that. The 
 processes by which we detect failures and handle them varies a lot though 
 and the "right" way to deal with failures has been a topic of discussion g
 enerally only eclipsed by how to do packaging and how to format code.\n\nD
 ifferent languages\, platforms\, and frameworks all not only handle errors
  differently but frequently have entirely different ways of thinking about
  what an error even is. I'd like to take you on a bit of a philosophical e
 xploration about what happens when things go wrong\, how we know they've g
 one wrong\, and what we do about it.
DTSTAMP:20260404T055633Z
LOCATION:Barn
SUMMARY:State of Exception(s) - Benno Rice
URL:https://pretalx.northbaypython.org/nbpy-2026/talk/QVQEP3/
END:VEVENT
END:VCALENDAR