Vorlesung "Einführung in die digitalen Geisteswissenschaften" #11 (7.7.2025)
Lisa Poggel Professur für Digital Humanities, FU Berlin
|
---|
Generally, when speaking of coding, it refers to writing code — for example, writing a Python script that sorts and renames files. Often coding is associated with writing scripts or simple programs that have one specific goal (e.g., download a dataset from an API or running a specific analysis on a dataset).
Programming goes beyond the simple activity of writing code; it encompasses planning, documentation, and an understanding of the bigger picture of the resulting program. Examples would be the generalization of a piece of code to be used by others or to be published as a package as well as the initial development of a web application.
Software engineering, in contrast, has an even more holistic view of the process of creating software. It does not only focus on the implementation of a program but also on its design by taking into account issues such as hardware, user, and infrastructure requirements. For instance, getting a web application to run locally on a laptop requires in many cases “just” programming. Adding test cases, setting up a continuous integration and delivery pipeline, making sure it can be deployed to different servers by externalizing configuration, and preparing it to be translated into other languages would require software engineering.
Quelle: https://github.com/dracor-org
Quelle: https://github.com/dracor-org
Quelle: https://github.com/python
“Should humanists learn to code?” Less than a decade ago this question would have ignited quite a controversy in the field of digital humanities (DH). Today, the consensus is that a certain level of code literacy is preferred. Instead of arguing whether code literacy deserves to be part of DH’s skill set, the debate has moved on to discussing what it means, exactly, to be code literate.
There is a debate whether the same quality standards that are used in professional software engineering projects should be applied to computational research. Some argue that scientific code does not have to follow software engineering best practices because the users of the code are programmers with in-depth knowledge of the internal workings of the code and hence don’t require it to be well documented or maintainable (Bull; Anonymous). We disagree. While it is probably true that a lot of code developed for research is only used within the same lab by a small group of people, this does not mean that they would not benefit from good documentation and coding best practices.
Beispiel aus Damerow et al.(2020)
Beispiel aus Stoltz und Taylor (2024)
Beispiel aus Damerow et al.(2020)
Quelle: https://lehkost.github.io/
Quelle: https://dhcr.clarin-dariah.eu/