cover

todo

VERY IMPORTANT: I should state very very clearly what it is that I am doing. Also that a huge majority of the code is software engineer code, and that code poetry are just distinctly related.

recs from guido, neuropsychologists who might be interested:

séminaire adrien puignot: principe de la sémiotique sociale, i.e. la fabrique de sens globale.

architexte: L’ensemble des catégories générales, ou transcendantes -types de discours, modes d’énonciation, genres littéraires, etc.- dont relève chaque texte singulier (genette). En gros, la méta-catégorie des catégories. Ce qui gouverne le texte. L’outil d’écriture n’est pas neutre, il impose des formes éditoriales et des formats d’écriture au scripteur. Il permet aussi la recomposition des “traces” de lecture (échange, co-construction, démantèlement)

infra-ordinaire: infra-ordinaire en tant qu’observation attentive de « ce qui se passe chaque jour et revient chaque jour, le banal, le quotidien, l’évident, le commun, l’ordinaire, l’infra-ordinaire, le bruit de fond, l’habituel. l’attention portée aux détails du réel apparaît comme une constante qui finira par devenir une théorie rassemblant la pensée et la pratique littéraires de l’auteur

add this to examples, from the rust parser example i forked, as an example of how people assign quality to proper scale naming:

rust // Level-change Operator (what a stupid name) operator_level = { operator_exp | operator_subscript | operator_exp ~ operator_subscript | operator_subscript ~ operator_exp }

quote from peter neumann: “these techniques may have enormous value in providing nontrivial assurances that the system might actually do what is expected of it . “ - “There are many problems arising in complex systems that must be thoroughly comprehended, but that once understood can be structured in a way that conceptually simplifies the design”

Include the fact that aesthetics help compress, and by compressing, people can hold more things in short term memory

Include Gordon Graham - Philosophy of Art and Aesthetics

include somehow:

```text struct

Brenda Baker undertook her Fortan-to-Ratfor converter against the advice of her department head–me. I thought it would likely produce an ad hoc reordering of the orginal, freed of statement numbers, but otherwise no more readable than a properly indented Fortran program. Brenda proved me wrong. She discovered that every Fortran program has a canonically structured form. Programmers preferred the canonicalized form to what they had originally written. https://web.archive.org/web/20200315093052/https://minnie.tuhs.org/pipermail/tuhs/2020-March/020664.html ```

conclusion

ENHANCE CLARITY

chap 5 - programming

in the last section, 5.3

chap 4 - understanding

meeting with nick 14.14

overall, I should keep in mind that I do not have a technical audience, and I should rework/remove a lot of the examples, and add extensive discussions and rationale as to why those examples are there

I should also address the status of AI-generated code (include, not include? I consider it the same as compiler code).

For Languages of Art, two things about exemplification vs. implementation:

In architecture, highlight the fact that the detail is the point of interaction between the human and the structure.

meeting with nick 07.04

chap 3 - beauty

tex % \begin{align} % \sqrt{2} & = p / q \\ % \sqrt{2} * q & = p \\ % p & = \sqrt{2} * q \\ % (\sqrt{2})^2 & = (p/q)^2 \\ % 2 & = p^2 / q^2 \\ % p^2 & = 2 * q^2 % \end{align}

meeting with nick - 28.12.2022

side note: are metaphors related to space because it’s hard for us to think in terms of time?

chap 2 - understanding

Also, Fuller’s taxonomy, derived from Bloom’s taxonomy. It is represented by two semi-independent dimensions, Producing and Interpreting. Each dimension defines hierarchical linear levels where a deeper level requires the competencies from the previous ones. Producing has three levels (None, Apply, and Create) and Interpreting has four (Remember, Understand, Analyze, and Evaluate). \citep{fuller_developing_2007}

intrinsic characteristics of cs:

chap 1 - ideals

https://aosabook.org/en/index.html -https://aosabook.org/en/zeromq.html - [ ] pare down! - [ ] in the listings, extend the caption to show the relevance of the snippet (e.g. for listing 8, neither is said about APL or about Game of Life: how should readers know this is relevant?) - [ ] for stats comparing different software (windows2000, wp, kirby), use a chart to make the point much quicker - [ ] justify the comparison between win2000 and kirby (differences in size, date of creation) - [ ] also explain a bit more fast sqrt (greg walsh must have had a deep knowledge of ieee floating points standards) - [ ] fig. 10: original is color coded, but also too hard to comprehend. magmarize would be a better example - [ ] move listing 10 to understanding computers - [ ] one liner: monostiche - [ ] since the chapter is too long, paraphrase code, rather than quote it - [ ] listing #2, not style but voices - [ ] black perl is still in old mode - [ ] explain listing 13 - [ ] table of listings: this is what the work is about (variety, meaningful, captioned; the caption is also for me cause it shows i am able to express concisely why the example is there)

introduction

structure notes

ide notes

general

~~look into the pdf “program text, style, laber” by brian lennon to address comments in microsoft windows source code~~

~~yullil - code art brutalism refers the HACKMEM document from 1972 MIT, related to architecture.~~

~~communautés épistémiques et communautés de pratique (Cohendet et al., 2001) -> Cohendet, Patrick, Creplet, Frederic & Dupouet, Olivier. « Organisational innovation, communities of practice and epistemic communities : the case of Linux ». In Economics with heterogeneous interacting agents~~