Group Discussion 2: Project Plan and TimeLine

Investigating deeper into programming languages and how they are structured led to more questions on how can constraints on languages influence the programmer and their culture around them. How will making the invisible( the code) visible in writing a narrative in code, have the same comprehensional level as conventional text. Will the code adopt the same discord or compatability of everyday languages(1).

On our second meeting ( Isaac, Zafaran, myself), we came with an idea of an artifact that reflects some of these questions. As most programs use English to construct an executable code, what if we reveresed the process of writting, and used the key words of a program in constructing a small text piece. We agreed to try it out, using C++ key words, and see what we can come up with for our next meeting. When deciding on a topic to write about, we randomly chose a wikipedia page that gave us a page about “Harold Warris Thompson” (2), although it was a biography of a person, we wanted to observe in what way each of us will narrate his/her story in a coding language.

Other ideas that came up in our meeting was using IBM Watson’s personality insights (3) where you can drop in any text and it performs a linguistic analytics and personality theory on the text used, in our case it was the code text that we randomly picked up from a code website, the results were funny and interesting, but it did not add any speculative answers to our questions.

Another idea was doing a performance between us, where the dialog would be the syntax of a programming language to see how that reflects on us and the listeners, and persue where that takes us. I believe there is a potentiality in the idea, in that making the invisible visable, and investigating how that reflects on the speaker and the listener. We ended up on deciding to try out writting a narrative short bio on Thompson using code, and share what we come up with for our next meeting. Ended our discussion by preparing a project plan and a timeline for Helen’s class next week.

— — — — — — — — — — — — — — — — — — — — — — — — —

(1) David Hilbert Dreamlike Program



One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.