@ -5,9 +5,9 @@ description: hello this is a log of francesco
Hello these are some logs from kamo. I like to develop software to inhabit complexity with visual and performative outcomes. You can find here a lot of works in progress and some finished projects. My resolution for these 2 years is to get good in documenting things I do.
So this is basically workout.
Read thesis in progress here --> [software and worlding](thesis/)
@ -30,4 +30,9 @@ What about these workshops? They are a way to share small prototypes that otherw
## Next worksiops
- __Closed captions as timeline__. How to use subtitles file to create time-based interactive web pages. See [subp](https://git.xpub.nl/kamo/subp). Could be interesting to open it up also to lens based students!
- __Git to web to print__. Setup a workflow for continuous work-in-progress publishing: write and design, pull push and print. See [Readme](https://git.xpub.nl/kamo/readme). Nice for thesis process :)
@ -15,18 +15,18 @@ _Documentation sessions to take care of code_
## What could it be
Periodical sessions where to document code.
Periodical sessions where to document code.
Once a week, a couple of hours, on a regular basis.
Soft facilitation:
- not meant to be frontal moments, but more a shared space
Soft facilitation:
- not meant to be frontal moments, but more a shared space
- small zines to share things about documentation practices (readings, frameworks, prompts)
- p2p feedback and help
- coffee snacks music
- stickers with animals that says document your code (wip)
- share progress like brief debrief ?
## For who?
## For who?
For people that tinker with code. Both novice and navigated ones. For documenting small ongoing prototypes or more structured projects. For xpub2, xpub1, lens based, even bachelor students? Something open.
## How to do
@ -35,7 +35,7 @@ For people that tinker with code. Both novice and navigated ones. For documentin
- Could be useful to have some examples
- Nice also to have some prompts
## Where ? ? ?
## Where ? ? ?
- March 23rd at varia
- Could ask v2 if it's somethig they are interested in
@ -51,14 +51,14 @@ Not sure but made a couple of flyers let's see
## Flyer text triouts
Document code like
Document code like
birds of paradise do
2 hours of headspace
to write some nice
_documentation_
for a more accessible
programming practice
2 hours of headspace
to write some nice
_documentation_
for a more accessible
programming practice
### Ok this is really not necessary right now but what about:
@ -79,8 +79,28 @@ Document code like
to write some nice
DOCUMENTATION
for a more <adj>
programming practice
programming practice
```
And with wobbly shapes for the flyer ...
but this will be for another time
### Let's write some text!!
points to touch on:
- code documentation
- couple of hours
- not just your code
Let's write some code documentation! For your new coding project, for the cryptic library you downloaded recently, for a script you want to share with others!
Too many pieces of code are left alone out there: without an entry point, invisible, while outside is raining
It's so nice when explanation of how a script works: wouldn't be great to take care
- notes for thesis: cycling along the river, documentation, learning a new language, esolang, exploring different ways of thinking
