You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
49 lines
2.7 KiB
Markdown
49 lines
2.7 KiB
Markdown
---
|
|
categories:
|
|
- GRS
|
|
- Writing
|
|
- Research
|
|
date: 21/09/2022
|
|
description: Graduate Research Seminar 2022-2023
|
|
slug: grs
|
|
title: GRS
|
|
---
|
|
|
|
## Session One
|
|
|
|
<!-- Be prepared to give an account of where you are at with your self-directed research and talk about what you want to achieve this year and what you want to do. Xpub students will talk about the work they have been doing on the Special Issues (individually and collectively). All students will be asked to consider what possibilities they wish to explore in the coming year.
|
|
|
|
Think concretely about what you want to make this year, how you are going to make it and why you are going to make it. Consider: What possibilities are open to you? (It is understood that making a final project is a process and things will change as you work on it). What material have you written (for previous presentations, descriptions of work , assignments for last year's methods class, the methods of annotation you developed &c) which you can use? Review the written feedback from tutors you got from previous assessments and have it available for reference during the first session. -->
|
|
|
|
### 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 (sleep talking),
|
|
- coding for others (yelling),
|
|
- and coding with others (singing)
|
|
|
|
- Formalize a methodology for coding as care
|
|
- that could be applied to different projects: from personal ones to collective to commercial.
|
|
|
|
- This could be done by intercepting different ongoing projects (from my artistic practice to freelance works and everything in between) and use them as case studies. Since they involve different kind of public they could provide different insights.
|
|
- The idea of the methodology is because of the very nature of Site Specific Software: every context is different, and instead of generalizing one solution for all it would be better to understand some principles to deal with each situation.
|