Code is Rhetorical?
Kevin Brock has set forth the perplexing idea of computer code as a form of persuasive communication. I quite literally scratched my head in confusion when reading Toward the Rhetorical Study of Code. I immediately shook my head in disagreement, but my wheels started to turn. I began to break this complex idea down until I had my own question to reflect on. I’m going to use this blog post to break down my thought process.
Code: Rhetoric for… a Machine?
In recognizing code as a rhetorical tool, my initial question reflected on the who of the matter. Last time I checked, code is primarily written for interpretation by machines, the computer: inherent compliers. Machines cannot interpret rhetoric, therefore there are no rules for consideration. A developer writes code, and the machine follows its syntactical instruction. The machine will not infer its code; it will simply follow it. Code is not aimed to persuade a machine, code’s functionality is to function properly, so the machine functions properly. Outside of developers, software engineers, and corporations, who is code meaningful to? I have never known machines to be persuaded by ethos, pathos or shit, kairos at this point!
Rhetorical Code: Operational, Not Persuasive.
Code is an instructional language; it is predictable and lacks the intent to persuade. Code’s only purpose is to perform tasks. Its success lies in its ability to execute correctly, not in its ability to persuade an audience. Right? For some reason, my mind will not allow me to fully disagree with this sentiment, and I want to disagree so badly. My brain connects this idea to Packer and Jordan’s five characteristics of new media: integration, interactivity, hypermedia, immersion and narrativity (Eyman 33). In relation to Manovich’s principle, I view Packer and Jordan’s view as the “front-end” view of the webpage and Manovich’s the “back-end”. This connection tickles my brain in the most uncomfortable way because I really, really would like to disagree with such a foolish idea. I have a thought that will not only age me greatly, but it kept me awake for an extra 30-minutes last night.
Rhetorical Coding Queen: Remembering Myspace.
The young adults might not ever understand this connection, but you might Professor Friend, so I’m going to talk to the other adult in the room here. Remember Myspace? The place where you intentionally built code to engage the audience? Its sole purpose was to entertain your audience. Every single code meant something. You see where I’m going with this, right? Please tell me you see where I’m going with this. This might be my next synthesis paper because my mind is reeling about this connection. I’m almost too giddy to continue. Yes, I’m going to leave you on a cliffhanger. You get it right?
Leave a Reply