### Name of the Software Curious Person: Donatella
### Situation: Dragging Linux Problem
### Description of situation at hand:
I am a linux user. I use excel sheer for my administrative work. I find that this software is not always efficient. My excel sheet stops very often, I am forced to close all my tabs and close my computer. So, I thought I should go to the clinic.
### Directed to Services: File Therapy Service
Something in the Middle Maybe
Continuous Integration
Future Blobservation Booth
Retrospection
### Total time available: 20
### Estimated Time for service: 20
### What would be a outcome:
Learn how to deal with this problem without having additional stress. Come out with a positive experience about this clinic. Consider the clinic a reliable place to come in the future.
### Evaluation
Very happy, a lot of new insights, got a therapy
all doctors were connecting to her and to the problem
felt very taken cared of
Future Blob: surpirsing at start, very relaxing experience, it gave her thoughts like the result of interaction is interesting, makes her think about liability of files and using certain programs, makes her understand that you have to look at it with different perspectives, not sthg stiff and done
### Exit status:
DONE
### Can this file be published:
YES
(if NO, print file says 'the file has been deleted')
Services
=======
# Something In The Middle, Maybe - Report
```
UDP 192.168.42.32:53649 -> 8.8.8.8:53
TCP 192.168.42.32:49250 -> 17.253.53.208:80
TCP 192.168.42.32:49250 -> 17.253.53.208:80
TCP/HTTP 17.253.53.208:80 GET http://captive.apple.com/mDQArB9orEii/Xmql6oYqtUtn/f6xY5snMJcW8/CEm0Ioc1d0d8/9OdEOfkBOY4y.html
TCP 192.168.42.32:49250 -> 17.253.53.208:80
TCP 192.168.42.32:49250 -> 17.253.53.208:80
TCP 192.168.42.32:49250 -> 17.253.53.208:80
UDP 192.168.42.32:63872 -> 8.8.8.8:53
UDP 192.168.42.32:61346 -> 8.8.8.8:53
UDP 192.168.42.32:52256 -> 8.8.8.8:53
UDP 192.168.42.32:65246 -> 8.8.8.8:53
UDP 192.168.42.32:59307 -> 8.8.8.8:53
UDP 192.168.42.32:53247 -> 8.8.8.8:53
UDP 192.168.42.32:55637 -> 8.8.8.8:53
TCP 192.168.42.32:49251 -> 173.223.106.91:80
TCP 192.168.42.32:49251 -> 173.223.106.91:80
TCP/HTTP 173.223.106.91:80 GET http://init-p01st.push.apple.com/bag
TCP 192.168.42.32:49251 -> 173.223.106.91:80
TCP 192.168.42.32:49251 -> 173.223.106.91:80
TCP 192.168.42.32:49251 -> 173.223.106.91:80
TCP 192.168.42.32:49251 -> 173.223.106.91:80
UDP 192.168.42.32:61250 -> 8.8.8.8:53
UDP 192.168.42.32:52952 -> 8.8.8.8:53
TCP 192.168.42.32:49253 -> 17.248.145.201:443
TCP 192.168.42.32:49253 -> 17.248.145.201:443
TCP 192.168.42.32:49253 -> 17.248.145.201:443
TCP 192.168.42.32:49253 -> 17.248.145.201:443
TCP 192.168.42.32:49253 -> 17.248.145.201:443
TCP 192.168.42.32:49253 -> 17.248.145.201:443
TCP 192.168.42.32:49253 -> 17.248.145.201:443
TCP 192.168.42.32:49253 -> 17.248.145.201:443
TCP 192.168.42.32:49253 -> 17.248.145.201:443
TCP 192.168.42.32:49253 -> 17.248.145.201:443
UDP 192.168.42.32:65107 -> 8.8.8.8:53
TCP 192.168.42.32:49253 -> 17.248.145.201:443
TCP 192.168.42.32:49253 -> 17.248.145.201:443
TCP 192.168.42.32:49254 -> 62.4.254.88:80
UDP 192.168.42.32:49918 -> 8.8.8.8:53
TCP 192.168.42.32:49254 -> 62.4.254.88:80
TCP/HTTP 62.4.254.88:80 GET http://gsp1.apple.com/pep/gcc
TCP 192.168.42.32:49254 -> 62.4.254.88:80
TCP 192.168.42.32:49255 -> 17.248.145.76:443
TCP 192.168.42.32:49255 -> 17.248.145.76:443
TCP 192.168.42.32:49255 -> 17.248.145.76:443
UDP 192.168.42.32:53985 -> 8.8.8.8:53
TCP 192.168.42.32:49255 -> 17.248.145.76:443
TCP 192.168.42.32:49255 -> 17.248.145.76:443
TCP 192.168.42.32:49255 -> 17.248.145.76:443
TCP 192.168.42.32:49255 -> 17.248.145.76:443
TCP 192.168.42.32:49255 -> 17.248.145.76:443
TCP 192.168.42.32:49255 -> 17.248.145.76:443
TCP 192.168.42.32:49255 -> 17.248.145.76:443
TCP 192.168.42.32:49255 -> 17.248.145.76:443
TCP 192.168.42.32:49255 -> 17.248.145.76:443
TCP 192.168.42.32:49256 -> 17.134.127.97:443
TCP 192.168.42.32:49255 -> 17.248.145.76:443
TCP 192.168.42.32:49257 -> 17.134.127.79:443
TCP 192.168.42.32:49256 -> 17.134.127.97:443
TCP 192.168.42.32:49256 -> 17.134.127.97:443
TCP 192.168.42.32:49257 -> 17.134.127.79:443
TCP 192.168.42.32:49256 -> 17.134.127.97:443
TCP 192.168.42.32:49256 -> 17.134.127.97:443
TCP 192.168.42.32:49256 -> 17.134.127.97:443
TCP 192.168.42.32:49255 -> 17.248.145.76:443
TCP 192.168.42.32:49255 -> 17.248.145.76:443
TCP 192.168.42.32:49256 -> 17.134.127.97:443
TCP 192.168.42.32:49256 -> 17.134.127.97:443
TCP 192.168.42.32:49256 -> 17.134.127.97:443
TCP 192.168.42.32:49255 -> 17.248.145.76:443
TCP 192.168.42.32:49256 -> 17.134.127.97:443
TCP 192.168.42.32:49256 -> 17.134.127.97:443
TCP 192.168.42.32:49258 -> 17.134.127.97:443
TCP 192.168.42.32:49259 -> 17.134.127.97:443
TCP 192.168.42.32:49256 -> 17.134.127.97:443
TCP 192.168.42.32:49258 -> 17.134.127.97:443
TCP 192.168.42.32:49259 -> 17.134.127.97:443
TCP 192.168.42.32:49258 -> 17.134.127.97:443
TCP 192.168.42.32:49259 -> 17.134.127.97:443
TCP 192.168.42.32:49258 -> 17.134.127.97:443
TCP 192.168.42.32:49258 -> 17.134.127.97:443
TCP 192.168.42.32:49258 -> 17.134.127.97:443
TCP 192.168.42.32:49258 -> 17.134.127.97:443
TCP 192.168.42.32:49259 -> 17.134.127.97:443
TCP 192.168.42.32:49258 -> 17.134.127.97:443
TCP 192.168.42.32:49260 -> 17.134.127.97:443
TCP 192.168.42.32:49259 -> 17.134.127.97:443
TCP 192.168.42.32:49259 -> 17.134.127.97:443
TCP 192.168.42.32:49259 -> 17.134.127.97:443
TCP 192.168.42.32:49259 -> 17.134.127.97:443
TCP 192.168.42.32:49259 -> 17.134.127.97:443
TCP 192.168.42.32:49258 -> 17.134.127.97:443
TCP 192.168.42.32:49258 -> 17.134.127.97:443
TCP 192.168.42.32:49258 -> 17.134.127.97:443
TCP 192.168.42.32:49260 -> 17.134.127.97:443
TCP 192.168.42.32:49260 -> 17.134.127.97:443
TCP 192.168.42.32:49259 -> 17.134.127.97:443
TCP 192.168.42.32:49259 -> 17.134.127.97:443
TCP 192.168.42.32:49259 -> 17.134.127.97:443
TCP 192.168.42.32:49259 -> 17.134.127.97:443
TCP 192.168.42.32:49259 -> 17.134.127.97:443
TCP 192.168.42.32:49259 -> 17.134.127.97:443
TCP 192.168.42.32:49260 -> 17.134.127.97:443
TCP 192.168.42.32:49260 -> 17.134.127.97:443
TCP 192.168.42.32:49260 -> 17.134.127.97:443
TCP 192.168.42.32:49260 -> 17.134.127.97:443
TCP 192.168.42.32:49260 -> 17.134.127.97:443
TCP 192.168.42.32:49260 -> 17.134.127.97:443
TCP 192.168.42.32:49260 -> 17.134.127.97:443
TCP 192.168.42.32:49260 -> 17.134.127.97:443
TCP 192.168.42.32:49260 -> 17.134.127.97:443
TCP 192.168.42.32:49260 -> 17.134.127.97:443
##################################################
Destination Address: 17.253.53.208
Destination Name: nlams2-vip-bx-008.aaplimg.com
Port: Connection Count
80: 6
##################################################
Destination Address: 17.134.127.79
Destination Name: unknown
Port: Connection Count
443: 2
##################################################
Destination Address: 17.248.145.201
Destination Name: unknown
Port: Connection Count
443: 12
##################################################
Destination Address: 173.223.106.91
Destination Name: a173-223-106-91.deploy.static.akamaitechnologies.com
Port: Connection Count
80: 7
##################################################
Destination Address: 17.134.127.97
Destination Name: unknown
Port: Connection Count
443: 51
##################################################
Destination Address: 62.4.254.88
Destination Name: 88.254-4-62.akamai.com
Port: Connection Count
80: 4
##################################################
Destination Address: 8.8.8.8
Destination Name: google-public-dns-a.google.com
Port: Connection Count
53: 13
##################################################
Destination Address: 17.248.145.76
Destination Name: unknown
Port: Connection Count
443: 16
```
# Rsoc - Relational software observatory Consultancy service
# "What is it like to be an elevator?"
# Interface Détournement
# File therapy
As our motto goes, 'the bigger the file, the bigger the problem'
Her spreadsheets occupy too much space. She is downloading them from her email address. She receives an Xray of the European document she has provided. It looks very chaotic. Lidia identifies the problematic area, she circles it on the page. She says she never looks at her file in such a way. We have spotted two problems. Martino opens the European document and modifies it. IT is not a problem to do so, because the European document has been blessed by the European commission. It is a public document. Martino shows the part that is human readable. Donatella now knows how the machine sees her document. She is inquisitive because she wants to communicate better with her machine. Donatella is correcting/corrupting the file. The new file is saved. Donatella feels better. Lidia is amused by the possibility of signification. Signification was an autocorrect from sonification. It sounds calming. The professional therapeutic advice is to use the file when going to sleep. Lonneke picks up a bit of tape from Donatella’s sweater. Martino asks if anyone wants something to drink. Lidia is professionally musing “this was working yesterday…”.
She is sent for further interventions to the Process Invocation service.
The observer overhears Donatella from the other side of the room. She sounds satisfied with our service.
# Process invocation
After a File Therapy, Donatella approached PI. Asking why she was sent to us for treatment, she explained that her wonderings about file weren't complete without a proper look at the reality of 'file processes'.
PI explained Donatella that a file is never really 'still', that there are processes running all along even when we think that we are not 'doing' something with it. PI showed a practical example of this by running 'ps aux | grep process', using mousepad as a process example. After having retreived the process number, we runned 'strace', to observe at the file's workings. Donatella was nicely surprised to notice that, even when the file seemed empty and 'unused', a great deal of processes where taking place before her eyes, on the terminal window (for example just by running the cursor on the empty mousepad window).
# Agile Sun Salutation
# Continuous integration
# Techno-galactic software walk-in clinic Reception
# Intake
# Future Blobservation Booth
# Retrospection
# Refreshment
# WTC-time
# Flow of the chart - chart of the flow on demand!