User:Francesco: Difference between revisions

From XPUB & Lens-Based wiki
No edit summary
Line 1: Line 1:
== Reading as a timelapse ==
== Reading as a timelapse ==


Hello these are some writings from <span style="border: 1px solid currentColor; border-radius: 1em; padding: 0 0.25em">kamo</span>. I like to develop software to inhabit complexity with visual and performative outcomes.  
Hello these are some writings from <span style="border: 1px solid currentColor; border-radius: 1em; padding: 0 0.25em">kamo</span>. I like to develop software to inhabit complexity with visual and performative outcomes. I think about programming as about magic: before there is nothing and then something new exists. I remember that when I was a child I used to think the same thing about drawing: lucky ones those who can draw (i was not), they can have everything at will. Who knows what will come next, say: in 20 years? The problem with technology is that you always end to walk at the same time above the <span style="border: 1px solid dodgerblue; border-radius: 1em; padding: 0 0.25em">waters</span> and above <span style="border: 1px solid tomato; border-radius: 1em; padding: 0 0.25em">lava</span>. Technical issues sprout from everywhere all the times. This is bad because they kill the relax. But it is also nice in the way that encourages collaborations and plural approaches to face problems.


I think about programming as about magic: before there is nothing and then something new exists.
== Soupboat ecosystem ==


I remember that when I was a child I used to think the same thing about drawing: lucky ones those who can draw (i was not), they can have everything at will.  
I dont like to write here in the wiki, sorry. As I prefer my notebooks to be clean instead of squared or lined, I also like to be more in control when it comes to keep track of my progress. Sorry again! So I'm working more on the [https://hub.xpub.nl/soupboat/~kamo/ Soupboat] right now. In the past few days I tried to set up a super minimal framework to store the results and explorations we do during classes. Even if super simple I like it, because it helps me doing something I really suck at: documenting my work.  


Who knows what will be the next step, so to say: in 20 years? 
=== Structure ===
feel free to edit if you see some sort of pattern here


From making things exist to making things do stuff to ......... to ......... to .......... ???
My folder in the Soupboat is a table that works as an index for all the projects I worked on since the first week at XPUB till → now.
(imagine a crossover between that nine inch nails album ↓ and the purgatory of dante ↑)


The problem with technology is that you always end to walk at the same time above the <span style="border: 1px solid dodgerblue; border-radius: 1em; padding: 0 0.25em">waters</span> and above <span style="border: 1px solid tomato; border-radius: 1em; padding: 0 0.25em">lava</span>.
At the moment ''v0.1 and super wip'': it keeps track of the following properties for each project:
* A title
* A list of links (often a pad and a git repo)
* A list of tags
* A date


Technical issues sprout from everywhere all the times. This is bad because kill the relax. But is also nice in the way that encourages collaborations and plural approaches to face problems.
Next features will be:
* Filtering through the tags (as in the [https://hub.xpub.nl/soupboat/~kamo/10-06-2021-chat_reader/chat.html chat reader]
* Differents ways of sorting


now im tired ciao
The contents are loaded from a .json file in the Soupboat, because after the third project it was too stressful for me the idea of adding new contents via markup. Is this stupid?
Someone said to me that it is not a good idea to rely only on the Soupboat because it is fragile and prones to accidents. It would be better to consider some forms of backup? Need to ask to Manetta and Michael and Aymeric.
 
Another thing that bugs me really really really a lot is the workflow in Jupiter. Need a better solution, maybe connecting git?
I saw some extension in the Jupiter Lab, need again to ask.

Revision as of 02:05, 13 October 2021

Reading as a timelapse

Hello these are some writings from kamo. I like to develop software to inhabit complexity with visual and performative outcomes. I think about programming as about magic: before there is nothing and then something new exists. I remember that when I was a child I used to think the same thing about drawing: lucky ones those who can draw (i was not), they can have everything at will. Who knows what will come next, say: in 20 years? The problem with technology is that you always end to walk at the same time above the waters and above lava. Technical issues sprout from everywhere all the times. This is bad because they kill the relax. But it is also nice in the way that encourages collaborations and plural approaches to face problems.

Soupboat ecosystem

I dont like to write here in the wiki, sorry. As I prefer my notebooks to be clean instead of squared or lined, I also like to be more in control when it comes to keep track of my progress. Sorry again! So I'm working more on the Soupboat right now. In the past few days I tried to set up a super minimal framework to store the results and explorations we do during classes. Even if super simple I like it, because it helps me doing something I really suck at: documenting my work.

Structure

My folder in the Soupboat is a table that works as an index for all the projects I worked on since the first week at XPUB till → now.

At the moment v0.1 and super wip: it keeps track of the following properties for each project:

  • A title
  • A list of links (often a pad and a git repo)
  • A list of tags
  • A date

Next features will be:

  • Filtering through the tags (as in the chat reader
  • Differents ways of sorting

The contents are loaded from a .json file in the Soupboat, because after the third project it was too stressful for me the idea of adding new contents via markup. Is this stupid? Someone said to me that it is not a good idea to rely only on the Soupboat because it is fragile and prones to accidents. It would be better to consider some forms of backup? Need to ask to Manetta and Michael and Aymeric.

Another thing that bugs me really really really a lot is the workflow in Jupiter. Need a better solution, maybe connecting git? I saw some extension in the Jupiter Lab, need again to ask.