BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//programme.europython.eu//europython-2026//speaker//WGFN
 BF
BEGIN:VTIMEZONE
TZID:Poland
BEGIN:DAYLIGHT
DTSTART:20250717T000000
TZNAME:CEST
TZOFFSETFROM:+0200
TZOFFSETTO:+0200
END:DAYLIGHT
BEGIN:STANDARD
DTSTART:20251026T030000
RDATE:20261025T030000
TZNAME:CET
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20260329T030000
RDATE:20270328T030000
TZNAME:CEST
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
SUMMARY:Design Pressure: The Invisible Hand That Shapes Your Code - Hynek 
 Schlawack
DTSTART;TZID=Poland:20260717T101000
DTEND;TZID=Poland:20260717T105500
DTSTAMP:20260823T012515Z
UID:pretalx-europython-2026-BK8GD8@programme.europython.eu
DESCRIPTION:Ever had this weird gut feeling that something is off in your 
 code\, but couldn't put the finger on _why_? Are you starting your project
 s with the best intentions\, following all best practices\, _and_ still fe
 el like your architecture turns weird eventually? Are you telling your AI 
 bot to write clean code but entropy keeps getting the best of you?\n\n**Ma
 ybe\, it's not your fault**! Maybe\, the tools or methodology you're using
  are applying **design pressure** that you're not cognizant of\, but that 
 influences the shape of your code.\n\nThe best way to prevent that is beco
 ming aware of the forces at play. So\, let's look at what design pressure 
 is\, look at the most prominent examples of good and bad\, and explore how
  to leverage the former and quell the latter. Because you can only deal wi
 th something you know exists.
LOCATION:S4
URL:https://programme.europython.eu/europython-2026/talk/BK8GD8/
END:VEVENT
END:VCALENDAR