BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//pretalx.c3voc.de//camp2023//speaker//VBUNRA
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-camp2023-CFASNP@pretalx.c3voc.de
DTSTART;TZID=CET:20230817T212500
DTEND;TZID=CET:20230817T214500
DESCRIPTION:Rebuilding target files when source files have changed is seems
  easy\, but is not. Commonly used build systems (make\, ninja\, etc.) are 
 often unable to guarantee both that they rebuild only what needs to be reb
 uilt and that they do not rebuild what does not need to be rebuilt.\n\nI w
 ill show how to reliably encounter common build system failure modes and e
 xplain which architectural choices lead to those. Using DJB's “redo” d
 esign as an example\, I will show how build system architecture determines
  if failure modes can be addressed at all. Lastly\, I will speculate why m
 any developers dismiss such issues before encountering them – and some e
 ven do afterwards.
DTSTAMP:20260715T013343Z
LOCATION:Milliways
SUMMARY:Fantastic build system failure modes and how to fix them - erle
URL:https://pretalx.c3voc.de/camp2023/talk/CFASNP/
END:VEVENT
END:VCALENDAR