# machine paradox The Machine Paradox week started with a random selection of objects in the lab. After cleaning them and bringing them to class, we split into groups to choose an object to analyse.

My group chose a DIY extruder made by previous IAAC students. {% embed url="" %} The first activity we carried out was to methodically take it apart, documenting each step and identifying the different components. This report allowed us to think critically about the functions of each component and how they contributed to the overall system. We then compiled a forensic report to ensure clear and complete documentation.

Disassembly of the main part by heat application

As our property had no electronic components, we also decided to examine a Fermax Wi-Box, a device that connects the home's video intercom system to a mobile phone, allowing remote access management.

This experience proved crucial for me, as it was my first time working with electronic components, and I found it interesting to learn how basic programming works and how to use libraries such as Bardino to interact with electronic boards. {% file src="/files/Aqq0n0OUVy7aYaeGRKd3" %} first time soldering cables!!!! {% endfile %} We were able to reuse the microphone and, thanks to a code and the use of Arduino, we were able to make ‘Mary Had a Little Lamb’ play. {% file src="/files/RiKSR9kKuIzLElCsUM0w" %}

*Project overview: exploration of uselessness* In this exercise, we were challenged to select components analyzed during the first week and reconfigure them into a functional structure that, while operating, ultimately serves no practical purpose. The purpose of this project is to explore emergent and alternative perspectives: how might something seemingly “useless” actually teach us something meaningful? Together with my team, we began by brainstorming possible ideas for a machine and its purpose. *Concept development and ideation* Our initial concept aimed to symbolize the arbitrary and unpredictable nature of life, emphasizing how circumstances beyond our control can shape individual outcomes. We envisioned each marble as representing a person born into a random life situation. As it rolls across a map, it lands in different positions—some fortunate, others not. This random assignment of outcomes reflects life's inequalities and prompts reflection on the question, “Why are some born with more privileges and opportunities than others?” Our team explored the question deeply: some believe it’s merely the “lottery of life,” a cosmic roll of the dice in which some are luckier at birth. Societal tools like education or policies may aim to level the playing field, but they can’t fully address disparities, nor can they “program” privilege or luck. Through this machine, we hoped to encapsulate this significant question: does the randomness of life predetermine our fate? However, due to time constraints, we decided to simplify the output to include only two sounds: one symbolizing “victory” and the other “defeat,” depending on where the marble lands. *Machine structure and operation* Our final design mirrors a simple children’s game in appearance, but it carries a layered, philosophical message. It functions through a motor-driven worm screw that guides a marble down a path. At the bottom, the marble lands randomly on a circular map representing the Earth. Depending on where it falls, the marble either drops into a slot for “luck and privilege” or one for “misfortune,” symbolizing the randomness of birth. *Key components:* Motor and worm screw: These were sourced from a dismantled 3D extruder. The motor powers a large screw that directs the marble along its path. Speaker: Recycled from an intercom system, the speaker plays the sound effects. Light sensors: These were added to enhance interactivity and detect where the marble lands. {% file src="/files/o2vhrHDL22JG9779fmdG" %} FORTUNA presentation {% endfile %} {% file src="/files/L8YpF0CTFmOCAF8nlLk8" %} FORTUNA video {% endfile %} --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://colombomariavittorias-organizati.gitbook.io/maria-vittoria-colombo-mdef/terms/term-1/machine-paradox.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.