From 306d6edf8f5517c8cf0513530f12b6676bc94cee Mon Sep 17 00:00:00 2001 From: km0 Date: Thu, 13 Apr 2023 17:04:19 +0200 Subject: [PATCH] im tired need to write conclusion --- chapters/02_backdoors.md | 9 +++++++++ notes.md | 4 ++-- 2 files changed, 11 insertions(+), 2 deletions(-) diff --git a/chapters/02_backdoors.md b/chapters/02_backdoors.md index 05ee5dc..8514fad 100644 --- a/chapters/02_backdoors.md +++ b/chapters/02_backdoors.md @@ -153,9 +153,18 @@ In the essay, they highlight how poetry often does offer rich context and a worl In the Screenless Office, the bureau aesthetic, with its collective imagery of characters, situations, and power dynamics, becomes a personal interaction design framework. Here the system is structured enough to articulate a complex application in a coherent, clear and legible way. And yet, the cosmology of the office remains open to contribuitions coming from elsewhere, say, another departement such as the `Canteen of the Screenless Office` inaugurated during a workshop with Howell at XPUB, with our own peculiar set of characters, aesthetics and documentation practices. +# wrapping up what did we learn + + + + + !!! placeholder "[ fade out towards outro ]" outro could be introduction of project and mention _care for code_ and doc sessions as a way to create entry points and pathways to read through this wealth of practices + + Code documentation as a backdoor because it can reach many different kinds of programmers, and in many different ways. + It works at different scales, from big projects to small gestures. diff --git a/notes.md b/notes.md index 063e00f..29d94aa 100644 --- a/notes.md +++ b/notes.md @@ -5,9 +5,9 @@ [x] transition to getting startled from entry point to backdoor [x] example paragraph padliography situate within larger context [x] and maybe connect it to aesthetic programming -[ ] outro code companion wrap up -[ ] context soupboat [could be in the appendix?] +[x] outro code companion wrap up [ ] outro +[ ] context soupboat [could be in the appendix?]