chapter 2: add reference to https://ieeexplore.ieee.org/document/8509170

src/thesis/2-reproducibility.typ

@@ -1233,10 +1233,12 @@ effectively. Nevertheless, this reliance on external components leads to the
 accumulation of both direct and indirect dependencies, complicating the software
 supply chain significantly. The build environments, which encompass all
 necessary components and their precise versions for software compilation, become
-intricate and challenging to replicate across different systems and over time.
-This complexity is often described as #emph[dependency hell]. While Semantic
-Versioning (@package-managers) offers a strategy to mitigate these issues, it
-alone is insufficient to ensure reproducibility
+intricate and difficult to replicate across different systems and over time.
+This growing complexity, "politely called #emph[dependency management]"
+#cite(<8509170>, form:"normal") but more colloquially known as
+#emph[dependency hell], is a phenomenon that developers have become all too
+familiar with. While Semantic Versioning (@package-managers) offers a strategy
+to mitigate these issues, it alone is insufficient to ensure reproducibility
 #cite(<TSE2019>, form: "normal", supplement: [p.11]).
 
 To illustrate this concept, the graph in

src/thesis/literature.bib

@@ -1036,3 +1036,15 @@ @misc{hinsenKonradFramework2020
   author = {Hinsen, Konrad},
   doi    = {10.59350/81ba8-dse91},
 }
+
+@article{8509170,
+  author   = {Dick, Stephanie and Volmar, Daniel},
+  journal  = {IEEE Annals of the History of Computing},
+  title    = {DLL Hell: Software Dependencies, Failure, and the Maintenance of Microsoft Windows},
+  year     = {2018},
+  volume   = {40},
+  number   = {4},
+  pages    = {28-51},
+  keywords = {Microsoft Windows;History;Software development;Software maintenance;Software engineering},
+  doi      = {10.1109/MAHC.2018.2877913}
+}