BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//programme.europython.eu//europython-2026//talk//HVTSPC
BEGIN:VTIMEZONE
TZID:CET
BEGIN:STANDARD
DTSTART:20001029T040000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
TZNAME:CET
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20000326T030000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3
TZNAME:CEST
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:pretalx-europython-2026-HVTSPC@programme.europython.eu
DTSTART;TZID=CET:20260715T143000
DTEND;TZID=CET:20260715T150000
DESCRIPTION:Conventions are one of Django’s greatest strengths.\n\nThey s
 implify our day-to-day work\, reduce cognitive load\, and let teams move f
 ast with confidence. By following well-established defaults\, we spend les
 s time debating structure and more time solving real problems.\n\nBut ever
 y convention is also a decision - and every decision has trade-offs.\n\nWh
 o decided these conventions? Why were they chosen? And what happens when y
 our problem doesn’t quite fit the “Django way”?\n\nIn this talk\, we
 ’ll explore Django’s conventions as both a feature and a constraint. W
 e’ll look at where they shine\, where they leak\, and how experienced de
 velopers can respectfully bend (or break) them without fighting the framew
 ork. This is a talk for anyone who loves Django — especially when they d
 isagree with it.
DTSTAMP:20260524T130633Z
LOCATION:Chamber Hall B (S3B)
SUMMARY:I Am a Sucker for Conventions. Why Django’s Defaults Work\, Until
  They Don’t - David Vaz
URL:https://programme.europython.eu/europython-2026/talk/HVTSPC/
END:VEVENT
END:VCALENDAR