BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//talks.godotengine.org//BV7FMT
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-godotcon-ams-2026-BV7FMT@talks.godotengine.org
DTSTART;TZID=CET:20260424T170500
DTEND;TZID=CET:20260424T173500
DESCRIPTION:A few months ago\, I found a Reddit post about a tiny pattern: 
 a cached getter. It solved a problem I'd been working around for some time
 . That sent me down a rabbit hole looking for more. Patterns that barely s
 how up in Godot tutorials. Stuff borrowed from backend engineering\, from 
 modern Python\, from the corners of Godot that everyone's a bit scared of.
 \n\nIn this talk\, I'll walk through the ones I keep reaching for now\, us
 ing code from the wave-based arena racing shmup I'm in the middle of shipp
 ing:\n- The cached getter from that Reddit post\;\n- The underused reposit
 ory pattern\;\n- The specification pattern\;\n- A lightweight dependency i
 njection pattern\n\nExpect code you can use on Monday and a few honest mom
 ents about what I'd do differently
DTSTAMP:20260428T181837Z
LOCATION:Theatre 1
SUMMARY:Game Programming Patterns for Godot - Inacio Schweller
URL:https://talks.godotengine.org/godotcon-ams-2026/talk/BV7FMT/
END:VEVENT
END:VCALENDAR
