User:C3/XPUB2/T4 Assessment
INTRO
During my first year I practiced coding and repurposing of old tech devices.
XPUB1
SI26
- web making as a craft
- outdated webstandards to hide or show information
- a game playable from one device
- situating our work within outdated webstandards, working withing limits limits.
- the game is the result of a learning and exploration process that did not find place into the final event.
SI26 with Doriane with the declarations project.
Exploring web making and web standards.
"SI26 3DS zine" A web game publication tailored to be played with the Nintendo 3DS game console.
We (Charlie, Tessa, Eleni and I) took advantage of the hardware specificity of the device (ex. 3D effect) together with outdated web-standards of its browser (Netfront, ex. opacity in % does not work while on the rest of the browser it does) to show/hide information from other devices, making our puzzle game solvable only through the use of the Nintendo 3DS.
It was a project about working withing the limits and showing the possibilities that lie within them.
Trought trial and error we noted a collection of strategies we used to make our project work.
SI27
- it contains a dialogue with Kim on the use of a server as a collective space.
- published on a server as a terminal publication
SI27 w/ Martino and Imane, researching the relationship between technological devices and time representation within them.
"SI27 Terms of servers" is a terminal based publication that runs on our server "cerealbox".
In this project, together with Kim, we considered our server as a temporal object. After working with it for a year (in classes, for the SIs projects and websites and for individual learning) we wrote a text that questions our use of it, its reliability and its materiality.
The text is then presented inside of the terminal with the use of a python program, intermitted by the use of live commands that output a partial answer of these questions inside of our publication. (like hardware compontents, uptime, to see how long the server has been running for, etc.)
XTRA
Some other threads that ran parallel to classes and Special Issues:
- hardware maintenance.
- scripting (especially python and bash).
- reading technical manuals like they were adventure books.
- finding playful ways of doing all of these things.
OPEN QUESTIONS
Overall, I see the cheatsheets as being an evolution/annex of my previous works, into a direction of documenting and distributing the processes that lie behind these and all of my projects. Most of these started as something that was not clear and that required observation to learn how to make possible, I feel like this method is something that is not tied to a medium in particular and that my aim of sharing mine is to also shine light on how might recognize their inner way of learning and listen to it by trying to bring it out.
SI26In the final outcome this part got a bit lost and I think the documentation and distribution of these tactics remained an unresolved topic for me, so I see the cheatsheets as a potential method to address both topics.
In the final outcome this part got a bit lost and I think the documentation and distribution of these tactics remained an unresolved topic for me, so I see the cheatsheets as a potential method to address both topics.
- and create my own documentation
XPUB2
trying to find an intersection between coding(prop), learning (focus) and playing(the way)
using different ways of learning than the manuals --> learning by playing and doing questioning the manuals and the cheatsheet as a form of distribution of the knowledge
WHAT
- project proposal: a series of workshop creating an iterative process.
WHY
DIAGRAM
THESIS PROPOSAL
research question: how do we navigate everyday tech saturation in an intuitive and playful way? What do we learn and how?