BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//pretalx.com//pycon-lithuania-2026//talk//GSMXRS
BEGIN:VTIMEZONE
TZID:EET
BEGIN:STANDARD
DTSTART:20000101T000000
RRULE:FREQ=YEARLY;BYMONTH=1;UNTIL=20011231T220000Z
TZNAME:EET
TZOFFSETFROM:+0200
TZOFFSETTO:+0200
END:STANDARD
BEGIN:STANDARD
DTSTART:20031026T050000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
TZNAME:EET
TZOFFSETFROM:+0300
TZOFFSETTO:+0200
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20030330T040000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3
TZNAME:EEST
TZOFFSETFROM:+0200
TZOFFSETTO:+0300
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:pretalx-pycon-lithuania-2026-GSMXRS@pretalx.com
DTSTART;TZID=EET:20260409T093000
DTEND;TZID=EET:20260409T103000
DESCRIPTION:Every team has code that makes them cringe. Legacy pipelines no
 body dares touch\, "temporary" tables that became the source of truth\, an
 d SQL queries that outlived three team leads. We call it technical debt\, 
 and the instinct is always the same: fix it.\n\nBut should we? After migra
 ting from Redshift to Snowflake\, learning PIG just to rewrite a pipeline 
 deprecated months later\, and surviving Airflow OOM kills\, I have opinion
 s. And maybe a framework slightly better than "it depends."
DTSTAMP:20260617T094357Z
LOCATION:Great hall\, (3rd building)
SUMMARY:Technical Debt: When to Pay It Down vs. When to Just Live With It -
  Tomas Peluritis
URL:https://pretalx.com/pycon-lithuania-2026/talk/GSMXRS/
END:VEVENT
END:VCALENDAR