User:Tancre/readings/Poetic software: Difference between revisions
< User:Tancre | readings
(Created page with "= Roidl - Poetic Software = Software is becoming omnipresent in our daily life, but it is taken for granted. >> understanding software (scientific, cultural, political, social...") |
|||
| Line 7: | Line 7: | ||
During the execution, machine code turns into physical current > act of poetic expression, in-between state with defined rhytmic, beyond human perception. Moment of transition, dependencies. | During the execution, machine code turns into physical current > act of poetic expression, in-between state with defined rhytmic, beyond human perception. Moment of transition, dependencies. | ||
Poetic software >> non-neutral and imaginative character of software used for artistic engagement. non-functional attributes + | Poetic software >> non-neutral and imaginative character of software used for artistic engagement. non-functional attributes + metaphors of software. Different layers of interpretation for an open interpretation. New artistic software beyond the interface and the expected mode of operation or depiction of software. Not needed to function but call for statements about issues of software. | ||
== 1 Reading == | |||
A close reading of Kittler's There is no software + becoming aware of the software being used:<br> | |||
* explosion implosion > compression-energy / expansion of digital-cables, buildings | * explosion implosion > compression-energy / expansion of digital-cables, buildings | ||
* dependencies > interrelation (loop) software-culture, shaping-being shaped | * dependencies > interrelation (loop) software-culture, shaping-being shaped | ||
| Line 15: | Line 15: | ||
* enclosure of the code > user-consumer / open, reusable / technical knowledge | * enclosure of the code > user-consumer / open, reusable / technical knowledge | ||
* abstractions & metaphors > SaaS / Manual - software as a tool, learn how to use software | * abstractions & metaphors > SaaS / Manual - software as a tool, learn how to use software | ||
* conceptual software > mental execution (cultural, political) VS only hardware (materialistic) / blurry boundary and tension between software-hardware | |||
* user interface > GUI hides processes, functions, source code, possibilities and the decisions taken / Needs for a human approach to software + humanization of software (skeumorphism) use of metaphors from the physical world to communicate complexities of the digital | |||
* non-functionality, error > misplacement or malfunction for knowledge / inconsistency & noise VS ideal perfection / processing & LeWitt | |||
* narratives > antropomorphization of computers (the media equation theory) / black-box for imagination / ELIZA, Clippy / make technology more understandable but misconceptions / fear of singularity after machine learning / narrative outside the software (software art) | |||
* noise > reintroduce noise, small glitches in software VS ideal perfection | |||
== 2 Writing == | |||
Revision as of 13:27, 2 October 2019
Roidl - Poetic Software
Software is becoming omnipresent in our daily life, but it is taken for granted. >> understanding software (scientific, cultural, political, social)
Gaps with art >> How can artistic methods be used to elicit critical reflection on software as a cultural object beyond the interface?
Current perception VS original culture, hacking
Software >> code(well researched) / compilation / execution (most abstract part) / manifestation (visible part)
During the execution, machine code turns into physical current > act of poetic expression, in-between state with defined rhytmic, beyond human perception. Moment of transition, dependencies.
Poetic software >> non-neutral and imaginative character of software used for artistic engagement. non-functional attributes + metaphors of software. Different layers of interpretation for an open interpretation. New artistic software beyond the interface and the expected mode of operation or depiction of software. Not needed to function but call for statements about issues of software.
1 Reading
A close reading of Kittler's There is no software + becoming aware of the software being used:
- explosion implosion > compression-energy / expansion of digital-cables, buildings
- dependencies > interrelation (loop) software-culture, shaping-being shaped
- language maze > framework-interface / diversity of languages
- enclosure of the code > user-consumer / open, reusable / technical knowledge
- abstractions & metaphors > SaaS / Manual - software as a tool, learn how to use software
- conceptual software > mental execution (cultural, political) VS only hardware (materialistic) / blurry boundary and tension between software-hardware
- user interface > GUI hides processes, functions, source code, possibilities and the decisions taken / Needs for a human approach to software + humanization of software (skeumorphism) use of metaphors from the physical world to communicate complexities of the digital
- non-functionality, error > misplacement or malfunction for knowledge / inconsistency & noise VS ideal perfection / processing & LeWitt
- narratives > antropomorphization of computers (the media equation theory) / black-box for imagination / ELIZA, Clippy / make technology more understandable but misconceptions / fear of singularity after machine learning / narrative outside the software (software art)
- noise > reintroduce noise, small glitches in software VS ideal perfection