BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//programme.europython.eu//europython-2026//speaker//RKEBR
 W
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-VSZSMW@programme.europython.eu
DTSTART;TZID=CET:20260717T135500
DTEND;TZID=CET:20260717T142500
DESCRIPTION:Three months ago\, I was hunting down a memory leak in our Flas
 k API that was driving me absolutely insane. The app would run fine for ho
 urs\, then suddenly RAM usage would spike and everything would crash. Prof
 ilers showed nothing useful. Logs were useless. My manager kept asking "is
  it fixed yet?" \n                                                        
                                                                           
       \n  In my desperation\, I started writing small Python scripts to tr
 ack every possible metric I could think of - not because I knew what I was
  doing\, but because I was running out of ideas. I tracked function call c
 ounts\, database connection pools\, even how many times certain variables 
 were accessed. Most of it was probably stupid\, but I was grasping at stra
 ws.\n                                                                     
                                                                    \n  The
  weird thing is\, those hacky little monitoring scripts I threw together i
 n frustration actually became the most useful debugging tool our team has 
 ever had. Not because they're sophisticated (they're definitely not)\, but
  because they were built by someone who was genuinely confused about what 
 was happening in their own code.\n                                        
                                                                           
                       \n  This talk is the story of how desperation led to
  accidentally building something useful\, and why sometimes the best tools
  come from not knowing what you're supposed to be doing. I'll show you the
  exact scripts I wrote (warts and all)\, the embarrassing assumptions I ma
 de\, and how you can steal these ideas to debug your own mysterious proble
 ms - even if you have no idea what you're doing either.
DTSTAMP:20260524T122005Z
LOCATION:Chamber Hall A (S3A)
SUMMARY:I Accidentally Built a Monitoring System While Trying to Debug Memo
 ry Leak - Goutam Tiwari\, Mohit Kumar Vyas
URL:https://programme.europython.eu/europython-2026/talk/VSZSMW/
END:VEVENT
END:VCALENDAR