BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Sabre//Sabre VObject 4.6.1//EN
CALSCALE:GREGORIAN
BEGIN:VTIMEZONE
TZID:Europe/Zurich
X-LIC-LOCATION:Europe/Zurich
TZURL:http://tzurl.org/zoneinfo/Europe/Zurich
BEGIN:DAYLIGHT
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
TZNAME:CEST
DTSTART:19810329T020000
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=-1SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
TZNAME:CET
DTSTART:19961027T030000
RRULE:FREQ=YEARLY;BYMONTH=10;BYDAY=-1SU
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
UID:news413@medienwissenschaft.philhist.unibas.ch
DTSTAMP;TZID=Europe/Zurich:20261027T150930
DTSTART;TZID=Europe/Zurich:20261113T091500
SUMMARY:What is Critical about Programming? Symposium on the History and Ph
 ilosophy of Programming
DESCRIPTION:Introduction\\r\\nIn the spirit of interdisciplinary inquiry in
 to programming\, this symposium will focus on "criticality in programming"
 \, and asking broadly "what is critical about programming?". Recalling the
  shared etymological root of "critical" with "crisis"\, we start from appr
 eciating a critical moment\, a crisis\, as that which requires a decision\
 , and thus sharp\, unambiguous judgment\, to dismiss any doubt. A crisis r
 equires a critical assessment of a situation\, and subsequent action\, con
 sidering programming as both a reflexive and decisive action.The initial c
 risis of programming\, the so-called "software crisis" in the 1960s\, was 
 addressed through hardening of practices (Dijkstra 2007). Critically asses
 sing the state of programming practices resulted in resolving a crisis by 
 changing how programming is done. \\r\\nHow was the engineering crisis co
 nceived of in the first place? Then\, what kinds of soft uncertainties wer
 e taken out to solve such a crisis? What kinds of methodologies (e.g. code
  reviews\, proofs\, tests\, perpetual beta) and arrangements (e.g. special
 isation and professionalisation) compose this hardening\, and how were jud
 gments passed as to whether the software engineering crisis had been avert
 ed? \\r\\nMore recently\, the development of tooling based on large langu
 age models might constitute a new critical moment. How should they be asse
 ssed when employed in the building of critical systems? What kind of crisi
 s might it represent to existing conceptions and histories of programming?
 \\r\\nOrganisation\\r\\nThe event is part of the History and Philosophy of
  Computation commission\, and is organized by Pierre Depaz (DHLab)\, Yanni
 ck Fritz (Medienwissenschaft) and Mace Ojala (Ruhr-Universität Bochum).\\
 r\\nRegistration\\r\\nAttendance is free\, please register by writing at b
 asel-2026@hapoc.org. Registration [mailto:basel-2026@hapoc.org?subject=Reg
 istration%20for%20Symposium%20on%20the%20History%20and%20Philosophy%20of%2
 0Programming]
X-ALT-DESC:<p><strong>Introduction</strong></p>\n<p>In the spirit of interd
 isciplinary inquiry into programming\, this symposium will focus on "criti
 cality in programming"\, and asking broadly "what is critical about progra
 mming?". Recalling the shared etymological root of "critical" with "crisis
 "\, we start from appreciating a critical moment\, a crisis\, as that whic
 h requires a decision\, and thus sharp\, unambiguous judgment\, to dismiss
  any doubt. A crisis requires a critical assessment of a situation\, and s
 ubsequent action\, considering programming as both a reflexive and decisiv
 e action.<br /><br />The initial crisis of programming\, the so-called "so
 ftware crisis" in the 1960s\, was addressed through hardening of practices
  (Dijkstra 2007). Critically assessing the state of programming practices 
 resulted in resolving a crisis by changing how programming is done.&nbsp\;
 </p>\n<p>How was the engineering crisis conceived of in the first place? T
 hen\, what kinds of soft uncertainties were taken out to solve such a cris
 is? What kinds of methodologies (e.g. code reviews\, proofs\, tests\, perp
 etual beta) and arrangements (e.g. specialisation and professionalisation)
  compose this hardening\, and how were judgments passed as to whether the 
 software engineering crisis had been averted?&nbsp\;</p>\n<p>More recently
 \, the development of tooling based on large language models might constit
 ute a new critical moment. How should they be assessed when employed in th
 e building of critical systems? What kind of crisis might it represent to 
 existing conceptions and histories of programming?</p>\n<p><strong>Organis
 ation</strong></p>\n<p>The event is part of the History and Philosophy of 
 Computation commission\, and is organized by Pierre Depaz (DHLab)\, Yannic
 k Fritz (Medienwissenschaft) and Mace Ojala (Ruhr-Universität Bochum).</p
 >\n<p><strong>Registration</strong></p>\n<p>Attendance is free\, please re
 gister by writing at basel-2026@hapoc.org. <a href="mailto:basel-2026@hapo
 c.org?subject=Registration%20for%20Symposium%20on%20the%20History%20and%20
 Philosophy%20of%20Programming" title="Registration">Registration</a></p>
DTEND;TZID=Europe/Zurich:20261113T173000
END:VEVENT
END:VCALENDAR