kamo-soupbato/projects/grs/documentation.md

categories	date	description	slug	title
GRS Writing Research	21/09/2022	Graduate Research Seminar 2022-2023	grs	GRS

Session One

What have you been making?

• Site specific software

• Developing custom tools in order to approach different needs

• Or materialize specific ideas to gain good grip on them.

• Different tools call different grips call different workflows call different outcomes

• Code as a shared practice: from coding alone to coding together

• Interaction between code and the community that surrounds it, how do they shape each other

• Coding as care, not control

• Writing code: balancing between accessibility, susteinability, flexibility.

• Writing after code: how to document and render works accessible, how to partecipate to the public discourse and create communities, how to mantain a project and how to let it go

What do you want to do next?

• Dig more into the difference between coding for oneself, coding for others, and coding with others

• Formalize a methodology for coding as care, that could be applied to different projects: from personal ones to collective to commercial. Ways of coding.

• How to: intercept different ongoing project (from artistic practice to freelance work) and use them as case studies. Since they involve different kind of publicness they could provide different insights.

Notes from the excercise with Miriam and Aitam

Find the pad here --> Group Discussion

And the trascription of what I said:

Hi, my name is Kamo

- how are you feeling about this year?
i am super excited, it is super exciting to get out of the xpub bubble, to talk to lens based,
i wanna find different degrees of publicness with my practice, it is interesting to make work accessible to people that don't have anything to do with your work
an understanding of what communities i am working with

- what strategies to make it more accessible?
making work interactive, but i am not interested in the idea of participatory art, it always comes with limitations, participation is way more complex than just pressing some buttons, i am interested in the idea of offering software, for this year at some point, i don't see myself focussing on one specific project but multiple alterations applied to different contexts, when i say "software" that's really generic, the chore project is methodology, i always work with the needs of the public, what if i make sth for a client that is already open source, involving the client into thinking this way, inviting to participate on this "openess", i am searching for a position related to certain issues, when you're coding, sustainability, accessibility and flexibility are parts of coding but they don't always have the same priority, for example making code accessible or sustainable for people who will use the code in the future, i would like to write a book about trolley problems, this is sth that interests me how these three pillars work together,

- references?
i learnt about software studies and i would love to dig into this, it is about considering software as a cultural object, to see everything that you see through the software lens as human and non-human beings, how softwares influence our perception of the world, but also zooming in and ask questions like what did control c did to writing? such problems.

- Why is it about the computer?
there is this materiality that could be really alien, it's a different interface to reality