kamo-soupbato/contents/recap.md

title	css	cover	cover_alt
Transcript of my assessment from the future	recap.css	recap/cover.jpg	dinosaurs

Hello

This months in XPUB were a lot of fun. At the beginning I was terrorized because of the moving, new people, new places, different language, so probably to cope with the stress I had an initial outburst of energies. Now I'm trying to stay calm.

Purpose

Lately I've been interested in programming. Probably because it's a playful way to interact with reality starting from abstraction. Something like theory but with instant and tangible outputs. Something like incantation or psychokinesis.

I'm into the development of site-specific software. Codes that inhabit and interact with a community. Coding as a form of care. Programming as a way to facilitate agency-on and comprehension-of complex systems. I'm learning how to approach complexity as an environment. How a work can be complex without forcing the result being complicated.

Methods

I like to propose ideas to the group. Sometimes the idea does not deliver , sometimes it lands but the results are catastrophic , sometimes the outcomes are unexpected , and sometimes they unexpectedly work .

My main interest is the ecology around these ideas. How it can be enriched and transformed by different voices, and the kind of play and space that it offers. I'm trying to shift from developing crazy things to developing meaningful things. Meaningful especially in relation to the environment and the other people involved in the process. To be meaningful an idea should stands on its own, but functioning as a starting point, more than a finite result.

I get easily bored-of or carried-away-by my train of thoughts, so I need to rely on others. That's why I always collaborate with someone else and rarely do things alone.

Outputs

Warm up

During the first month every day was a fest and we developed everything that came to our mind. To have the Soupboat felt empowering. A place to call home in the internet. Not really a critical approach maybe, but an ecstatic condition.

Together with Erica we tried to develop a shared cookbook , then a birthday cards collector to spawn best wishes in the Soupboat homepage at each birthday, some prototypes for the karaoke as a form of republishing , a way to track all our pads through the media wiki API.

During the group exercise I collaborated to the text lifeboats and different ways to weave texts together to generate new meanings, transforming a complex writings into an abstract chat , and the insecam livestream transcription .

SI16

I like what we did for the SI16. The concept of using an API as a form of pubblishing was mindblowing. The approach proposed during the prototyping sessions was extremely stimulating, even if sometimes frightening to rewind and rewind and redo things differently . I feel sorry if at some point I pushed for something that someone perceived as a failure. I get that it's a matter of perspective: from my point of view what's important is the process and the ways we work together, while for someone else a concrete outcome is more important. I need to keep in mind that both sides are legit and valid.

I contributed on the overall structure, the backend and the frontend , and the visual identity. The Concrete Label project started with Supi to annotate concrete poetry to create vernacular corpora became the Annotation Compass , a tool to annotate images collectively.

We managed to achieve a lot: a distribuited API, a familiar CMS based on Jupiter Notebooks , a coherent environment with room for customization, and a shared understanding of a complex topic . I tried to document these processes both in the soupboat and directly in the code . This required a lot of effort since I've always had a bad relation with documentation, probably because I'm an over-analitical-critical-shy person.

We failed in finishing things. The event-mode of the website as well as the API key circulation remain a draft. The workload was crazy, especially considered the technical difficulty of the overall project that led to unbalanced shares of work.

Slow down

After the winter break we slowed down, and spent more time studying the special issue's materials. Together with Erica, Mitsa, Chae, and Alex we read through all the text together. The ideology excercise with noise canceling headphones, the critical karaoke about gamification , the katamari fanfiction , the replace('mimic','loot box') research , and the gravitational approach to mapping the theme of gamification were all results of a moment with more critical focus on the contents and less on technical experiments.

At the beginning of the accademic year we applied to Room for Sound with the k-pub karaoke project, but timing and covid messed up with our plans, and in february after a couple of day of residency we decided to step back in order to focus more on less things. Room for Sound understood our needs and proposed us to retry later on this year.

The plan now is to continue working on the karaoke format as a moment in which different forms of public meet each others: there is a text and writing aspect, a musical and sonic one, it's a collective and personal performative moment, and it's something already present in the collective imaginary. So it could be a good generative device.

SI17

The process of SI17 was much more mindful than the previous one. As a group we put a lot of effort into the facilitation and organization of the work. The tired but cheering way we arrived at the launch is a sign of success.

The iterations of the work and the ideas were a lot, and the time passed on the readings was really effective to generate thoughts about the relations within the public, the jigsaw puzzle as a form of encryption of our contents, the loot box as a decorator or skin for other pubblications, ways to seal the boot lox instead of opening it, or ways to hack its inner temporality .

When we entered the production phase I worked with Mitsa, Supi and Erica as part of the team 1, in charge of the contents of the boot lox. We approached the different contents with the idea of a common ground such as the post-it. We worked with a surface to gather the contents and with another one to generate the results . When Supi said that the way we worked made her rethink inDesign I was happy. Even if the perceived workload at some point was insane (tell me more about the blurred line between leisure and labor), the overall experience was super great, and we managed to work well together with a common pace.

Things went wrong only in the last days before sending the print, when we didn't manage to share the work in a fair way. To me this was a great loss since it was the main stake of the entire process. We had several reflections about this and then managed to recover the group morale working together on the website.

To keep things simple is difficult, but important. At the end I think the issue website is great, since we did it altogether. It's not a problem if it's not technically interesting or flexible or modular or what else. I accepted that there are other parameters to create value and meaning. With the help of the group I also managed to give value to things I did such as the xquisite branch and the mimic-loot box research , that ultimately ended as contents in the final pubblication.

Some moments were super hard: a certain Monday during spring break we should have decided on something to move on, but every proposal was rejected. It was really difficult, especially since there were valid ideas on the table. Usually I'm not really attached to my proposals and I'm always ready to give up to something in favor of something else. What I find really difficult it's to give up to something without a real alternative.

Further developing interests

• How different forms of intelligence can interact with complexity (language, body, intuition, logic, emotion)
• Coding as a form of care instead of control
• Design pattern (OOP)
• Learn how to play the accordion.