BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//programme.europython.eu//europython-2023//speaker//7DHKE
 F
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-2023-FFTHXB@programme.europython.eu
DTSTART;TZID=CET:20230719T104500
DTEND;TZID=CET:20230719T111500
DESCRIPTION:Black\, Flake8\, isort\, and Mypy are useful Python linters but
  it’s challenging to use them effectively at scale in the case of multip
 le codebases\, in a large codebase\, or with many developers. Linter analy
 sis on large codebases is slow. Linters may slow down developers by asking
  them to fix trivial issues. Running linters in distributed CI jobs makes 
 it hard to understand the overall developer experience.\n\nIn this talk\, 
 we'll walk you through solving those scaling problems using a reusable lin
 ter framework that releases new linter updates automatically\, reuses cons
 istent configurations\, runs linters on only updated code to speedup runti
 me\, collects logs and metrics to provide observability\, and builds auto 
 fixes for common linter issues. Our linter runs are fast and scalable. Eve
 ry week\, they run 10k times on multiple millions of lines of code in over
  25 codebases\, generating 25k suggestions for more than 200 developers. I
 ts autofixes also save 20 hours of developer time every week.
DTSTAMP:20260513T152711Z
LOCATION:Terrace 2B
SUMMARY:Python Linters at Scale - Jimmy Lai
URL:https://programme.europython.eu/europython-2023/talk/FFTHXB/
END:VEVENT
END:VCALENDAR