aesthetics in software engineering is not about the program, it’s about the programmer.
the aesthetics of clarity in executable source code
questions of clarity vs. simplicity (how often do they correspond? oppose?) - is one within time, or within space, or within people?
semantics? -> programming languages have semantics (either denotational or operational, stratchey) -> operational is whatever the machine says, and we can realize/describe/use a symbol without understanding it -> understanding the symbol vs. understanding what the symbol refers to.
there is always a bit of giving up the understanding (linux kernel, APIs, etc.). does it remove the essence or in contrary highlight it?
STRATEGY VS. TACTICS
but tactics could actually be the tip of the manifestation of a yet unknown (the personal?) strategy. two months later: hmmm….
aesthetics as a relationship to the human: if tactics is what makes the individual, strategy is what forces the group > as code matures, there is a switch to a different kind of individuality (mass-production of code)
what is source code, as a ~~literary~~ linguistic object? (theoretical linguistics, craft linguistics, literary linguistics)
~~what are the useful conceptual tools that i use from the research on e-lit (e.g. combinations, potential, interactivity, … check the book by hannes bajohr, code und Konzept)?~~ these tools are cayley’s vocabulary, syntax, structure
done (separated in socio-economic categories of practicioners)
“efficient code” depends on knowing the material that you are working with: in the 1970s, it was the compiler (kernighan, elements of programming style). in the 2000s, it might be just the language spec.
code as substitute-material
expressing vs. explaining (Kurosawa) / hinting at (Tolstoi) important ideas to keep
‘There is no such thing as elegance or subtlety in the way I use software.’ Belgrade-based sound artist Svetlana Maraš > there are other aesthetics: brutality, organicness, rococo, etc. elegance and subtlelty are only subsets, but very very large ones
what are the parallels and separations between lit and code? still not figured out
In linguistics, prosody is concerned with those elements of speech that are not individual phonetic segments (vowels and consonants) but are properties of syllables and larger units of speech, including linguistic functions such as intonation, tone, stress, and rhythm. Such elements are known as suprasegmentals. Prosody may reflect various features of the speaker or the utterance: the emotional state of the speaker; the form of the utterance (statement, question, or command); the presence of irony or sarcasm; emphasis, contrast, and focus. It may otherwise reflect other elements of language that may not be encoded by grammar or by choice of vocabulary. (wiki)
~~can source code support multiple readings? should it?~~ depends on the context. on the engineering side, it should have only one meaning. on the education side, it could have gradual meanings. on the artistic side, it could have parallel meanings.
however, source code doesn’t seem to have any depth: it is what it does > but hidden depths have to do with the nature/function of the work and the social field in which it exists “What it means for something to have “depth” is that its explanation requires bringing in something like that, something of a different nature, something that does a kind of work no additional detail ever could.” depth is different from detail perceivable (but still hidden) vs. shown looking harder vs. looking differently
Some colleagues (such as Thomas Kühne from Victoria University of Wellington) have taken this further to explicitly define the limited properties of any model. Kühne (2005) describes this in three ways:mapping–(i.e. acknowledging that models are projections of an original);reduction–(i.e. acknowledging that models only represent a selection of relevant properties of the original); and pragmatics–(i.e. acknowledging that any model isaccepted as a proxy for the original only for a specific purpose).
problematiques importantes: dispositifs et mediations
DRY is actually a problem: humans understand if you repeat them over and over. how do you compromise that? -> proof of the multiplicity of contexts
IS THERE A RIGHT WAY TO WRITE BEAUTIFUL CODE? no, it depends on contexts
acknowledgment of socio-cultural context within which code poetry emerges, then formal examination of language through which these are written, and circling back towards what these formal uses have to contribute about the purpose/meaning of writing source code poetry (communities, hackers, exploitative economic systems, etc.), and allow for a new perspective on contemporary literature.
~~Is there something that makes something inherently beautiful? As relations to humans/human condition of that time -studying tools.~~ i would argue it’s “attention to readership”
esolangs have a “wimpmode”: esolangs do imply some sort of “skill”. wimpmode is the implication of different readerships
there is also the idea that, even when the code might not work properly, or might barely work (in a functional perspective), it might still work in a literary perspective, the same way that flaubert works, or that beckett works, i.e. does what is intended of it to do (how do we know that? we need critical tools to assess the “aestheticity”). we also need to assess what it is that it is intended to do.
what is the difference between poetics and aesthetics? poetics put together an effect (formal, subjective) vs. aesthetics are more universal, inherent, contemplative? solved
the role of case studies: develop an outline from looking at code, then confront that outline (which will probably be multifaceted) with case studies (2-3) solved
how is the aesthetic value of source code different from the aesthetic value of digital art? irrelevant