HiST How programming language influence interaction and culture Ivar Tormod Berg Ørstavik.

of 19/19
HiST How programming language influence interaction and culture Ivar Tormod Berg Ørstavik
  • date post

    20-Jan-2016
  • Category

    Documents

  • view

    215
  • download

    0

Embed Size (px)

Transcript of HiST How programming language influence interaction and culture Ivar Tormod Berg Ørstavik.

How programming language influence interaction and cultureIvar Tormod Berg Ørstavik
HiST
What are the reciprocate dialectics between human minds and ICT?
HiST
Strategically choose social theories on language and language use
But how to get that?
HiST
Dialogism
HiST
A social semantic focus
Social structures are seen not only side by side with language, but also as within language itself.
To understand language we need to understand the interaction that surrounds it.
HiST
Analysis
’path-relative types’ in Python (and Java)
’URL-types’ in theJ
print "</html>"
def getText(node):
printDocument(document)
HiST
c) update path
Words interpreted within
Words depend on each other to function and make sense
class MyClass { ClassA a = ClassB.work(); }
class ClassA { ClassC c = ClassE.do(); }
class ClassB { ClassD d = ClassC.work(); }
class ClassD { for (…) ... }
class ClassC { if (…) ... }
class ClassE { while (…) ... }
class OtherE { while (…) ... }
class Some { while (…) ... }
class Thing { while (…) ... }
class Strange { while (…) ... }
class Strange { while (…) ... }
class Strange { while (…) ... }
class Strange { while (…) ... }
?
?
?
?
Social interaction with words
Path-relative type morphology does as much for programming as the concept of a leather ball and an enclosed pitch does for soccer.
Reciprocally programmers can ‘hide’ incomprehensible problematic details from other programmers who can then ‘neglect’ to learn and focus on these details (cf. Shute 2006).
HiST
’Terms’ and intentions are associated with using others words
Look ahead! Chains of dependencies between words cause social and practical problems.
HiST
class ClassD { for (…) ... }
class ClassC { if (…) ... }
class ClassE { while (…) ... }
class OtherE { while (…) ... }
class Some { while (…) ... }
class Thing { while (…) ... }
class Strange { while (…) ... }
class Strange { while (…) ... }
class Strange { while (…) ... }
class Strange { while (…) ... }
class ClassA { for (…) ... }
class ClassB { while (…) ... }
HiST
Issuing standard libraries fix many practical problems.
But programmers outside this sphere wanting to team up still face problems.
This makes it easier for programmers to use the standard words, and harder for ’third parties’ to get their voice heard.
HiST
MAS – needed collaboration of Java code across different inter-textual run-time
In principle the same practical, social and technical issues as at design-time
Manual ’fixes’ not an option run-time
Could we change how we use morphological forms?
HiST
theJ
http://the.hist.no/thej.ExampleOne parserA =
Everyone are potential second parties
Everyone is untrustworthy and a security risk
HiST
Morphology changing actions
Resolves a technical problem using OO as an inter-program language run-time
Also, enables dangerous, but still freer use of ’third party words’
No standard library!
Openness key, write code in wikis
A new morphology gave a philosophical hindsight into old morphology
HiST
Rita Mae Brown