@ -118,63 +118,63 @@ Probably not so directly connected but there is this book (which one and where w
A methodology for software development as a form of care.
Research how writing software changes depending on the context and actors involved.
Bring the specificity of three different case studies: coding for oneself, coding for others, coding with others.
Bring the specificity of three different case studies: coding for oneself, coding for others, coding together with others.
How different nuances of these three settings can inform and resonate one with the other?
### How do you plan to make it?
The plan is to focus on three parallel projects of different nature.
The plan is to focus on three parallel case-studies of different nature.
One in which I develop for myself, one in which I develop for someone else, and one in which I develop together with some others.
Not all these projects need to start from scratch. This year could be the chance to inject some awareness and forms of care in already ongoing projects.
Not all these projects need to start from scratch. This year could be the chance to inject some awareness and forms of care in already ongoing works.
Developing for myself could happen in the context of [Object Oriented Choreography](../ooc-summer-session/), my long-term contemporary dance project with VR. What would it mean to bring XPUB forms of care into that work? What does it mean to develop for oneself in the context of coding as discourse?
Developing for myself could happen in the context of [Object Oriented Choreography](../ooc-summer-session/), a long-term contemporary dance research with VR. What would it mean to bring XPUB forms of care into that work? How could tools developed for personal needs participate to a broader discourse?
Developing for someone else refers to commisioned works and freelance work. Could it be a way to bring not only the advantages but also the perspective and cultural dynamics of FLOSS into commercial practices. Freelance work often comes to me in the form of web or interaction design and development. It could be a way to orientate specific commision to the development of tools of general use.
Developing for someone else refers to commisioned and freelance work. It could be a way to bring not only the advantages, but also the perspective and cultural dynamics of F/LOSS into commercial practices. My freelance work usually consists in developing websites or interactive application to be used in performative context. It could be a way to orientate specific commision to the development of tools of general use.
Developing togheter with others it's a way to rinegotiate priorities when developing software. How do we value and balance between accessibility, flexibility and sustenaibility? This could happen either collaborating with someone from XPUB (think for example to the [workbook](../workbook/) with supi, the ilizarov projects with gr, etc ) or intercepting some external realities' need to craft together some piece of site-specific software.
### What is your timetable?
**october**
define practically a method for the methodology: think about format and protocols
define the premises in which to ground the three projects by revisiting first year projects
get in touch with different communities for proj 2 and 3
**October**
Define practically a method for the methodology: think about protocols and possible formats for graduation project outcome.
Define the premises in which to ground the three projects by revisiting first year projects. Draw a political compass of software as care.
Get in touch with different communities for case study 2 and 3.
**november**
work on OOC preparing for december performance
develop context and prep-works for point 2 and 3: ideally setup temporality
try to reach key figure to ask
**November**
Work on OOC, preparing for December performance at NaO Festival, Milan.
Develop context and prep-works for case study 2 and 3: plan timetable.
Get in touch with key figures to interview for research.
**december**
ooc performance and follow up about findings for the methodology
**December**
OOC performance and follow-up about findings for the methodology.
**january**
start working on proj 2
start working on proj 3
**January**
Start working on case study 2.
Start working on case study 3.
**february**
working on one proj
update format and protocols
**February**
Work on one case study.
Update protocols and possible formats for graduation project outcome.
**march**
workin on the other proj
update format and protocols
**March**
Work on the other case study.
Update protocols and possible formats for graduation project outcome.
**april**
follow up about findings for the methodology
production for methodology outcome
**April**
Follow-up about findings for the methodology.
Production for methodology outcome.
**may**
production for methodology outcome
production for grad exhibition
**May**
Production for methodology outcome.
Production for graduation exhibition.
**june**
graduation exhibition
party
**June**
Graduation exhibition.
Party
**july**
siesta
**July**
Siesta
### Why do you want to make it?
@ -185,7 +185,16 @@ control, frame the world in a form that you can control and act on from a really
i would like to research on the question: can we do it in another way? giving back something and not only take
when you're using a tool you can learn the world throught the use of it, the difference is: can i use the scissors to cut a piece of paper and make a notebook or kill someone? -->
Software comes from a really specific and situated cultural tradition. Software tends to privilege occidental, masculine, binary, and extractive practices. Software comes with technical obscurity. Software comes invisible, transparent, neutral. Software models the world in order to better control it. I don't like these trends.
The following is a list of current trends that the software industry enforces and reiterate.
Software comes from a really specific and situated cultural tradition.
Software tends to priviledge occidental, masculine, binary, exploitative and extractive practices.
Software is shrouded with technical obscurity.
Software comes invisible, transparent, neutral.
Software models the world in order to control it.
Making software means not only to write code, but also to take a stance regarding this trends.
With this project the intention is to situate my practice within some ethical boundaries.
