[[contini_goodman_art_cognition_education]], summary of goodman and project zero
[[carroll_aesthetic_experience_revisited]] theory (affect, axiom, content)
[[chatterjee_vartanian_neuroscience_of_aesthetics]] psychology/cognition, fluency theory
[[goodman_the_status_of_style]], along with[[lopes_goodman_symbol_theory]]
[[goody_logic_of_writing]], goody comes here because he is dealing at the same higher level of the symbol system (orality vs. literacy), and then combine it with [[hayles_speech_writing_code]]
classical rhetoric has: 1. invention 2. disposition 3. memory 4. elocution 5. action
pierre fontanier, les figures du discours
beardsley [[beardsley_aesthetic_experience#15 - the metaphorical twist]]
burke and the terministic screen [[burke_language_as_symbolic_action]] and the scientistic language vs. dramatic language / wittgenstein and the formal-infomal
this section oscillate between the scientific reading/writing of a text and the dramatistic (sic) reading/writing of a text as a useful means of apprehending the dichotomy between formal and informal language plays in source code r/w. additionally, the concept of terministic screen (not so far from goffman’s frame analysis) will help us apprehend under which shifting social modes of examination code is being judged.
this section takes on barthes distinction between the readerly and the writerly text and sets it against the practice of open-source software and the tradition of craftsmanship in order to highlight that pleasure/life is being taken from reading readable source code. by looking at additional approaches that barthes has to writerly texts, those which leave room for interpretation, we will be able to identify similarities in source code, first in code structure (modularity), then in code text (conceptual and reader distance) and finally in meta-text, around the comment.
this section concludes our framework construction by enriching it with a relational component, which, while at least implicit in previous contributions, is here expanded on a more social level. it’s hard to separate an exploration of source code aesthetics while side-stepping the heightened features of the social group/s that programmers constitute. it might be possible to consider a piece of source as a “distributed énonciation”, both towards the computer and the fellow human, but also a “delayed énonciation”, because it isn’t as immediate. and because it isn’t immediate, there needs to be an adaptation of the concept of presence in craftsmanship; presence, a requisite in craftsmanship, is manifested through aesthetics. (
<- that indeed tells us why we need aesthetics, but doesn’t tell us what these aesthetics are. a closer reading of craftsmanship/aesthetics sources would however have more weight in light of this necessity for presence).
transition avec l’architecture: conception de l’architectural literature [[bouchardon_valeur_heuristique_de_la_litterature_numerique]]
[[gefen_extension_du_domaine_de_la_litterature]], broader level (see also his contribution in [[lavocat_interpretation_litteraire_sciences_cognitives]])
rousset: forme et signification
this section explores beauty from the angle of formal logic,
TODO. the conclusions could either be formal (like when cramer talks about the symmetrical, repetitive patterns of middle-age monks, or commentaries of mathematicians on
e^(i*PI) + 1 = 0), or conceptual. if they’re conceptual, they don’t need to come in to the framework right now.
http://emis.matem.unam.mx/journals/NNJ/conferences/N2004-Diaz.html - beauty in math and arch
beauty in math: https://en.wikipedia.org/wiki/A_Mathematician%27s_Apology
Abstraction in programming is the process of identifying common patterns that have systematic variations; an abstraction represents the common pattern and provides a means for specifying which variation to use. An abstraction facilitates separation of concerns: The implementor of an abstraction can ignore the exact uses or instances of the abstraction, and the user of the abstraction can forget the details of the implementation of the abstraction, so long as the implementation fulfills its intention or specification. (Balzer et al. 1989)
détour par le style de gilles gaston-granger [[granger_essai_philosophie_style]]
habitability (building is clear to move around)
sullivan (building is clear function) /
alexander vs. eisenman
alexander = softdev, habitable vs. eisenman = hack, subversion
design thinking book: The concept of good in architecture is one which says, among other things, that all architecture must engage its audience. It must foster understanding and be intelligible. This is clearly not the only concept necessarily at work, but it is one that would have broad adherence, across positions.
Compression is the characteristic of a piece of text that the meaning of any part of it is “larger” than that particular piece has by itself. This characteristic is created by a rich context, with each part of the text drawing on that context—each word draws part of its meaning from its surroundings. Piecemeal growth is the process of design and implementation in which software is embellished, modified, reduced, enlarged, and improved through a process of repair rather than of replacement
[[coburn_vartanian_neuroscience_of_architectural_experience]] cognition-wise there’s not a lot of research yet
[[downton_knowledge_architecture_science]], about bottom up knowledge, rather than strictly top down
lacaton & vassal: establishment of new aesthetics based on new needs
industrial architecture as a parallel with professionalization software developers?
[[gandesha_aesthetic_dignity_of_words]], praxis in language as a means of knowing, based on adorno’s philosophy [[wilken_card_index]], information architecture