Vitrinekast'ed annotated reader/Design For Hackability (Panel)
| Type | reading |
|---|---|
| Author | |
| Year | 2004 |
| Date read | 08/05/2024 |
| Source | https://www.researchgate.net/publication/221441240_Design_for_hackability |
| Tags | annotated_reader, |
Annotations
A description of a panel(????!!?) around Design for Hackability. Altho not a super interesting read, it does contain some good definitions of terms, which are relevant and I’d like to apply to the upcoming circuit bending workshops.
It’s also about ownership/.
Design for hackability
Keeping system open (lazy dev syndrome) So it can be adopted by the users more then just being able to modify, but be able to redefine. Create spaces for play, where people are not force to adapt to the technology/
Ownership
By hacking we reclaim authorship and ownership of technologies and the social and cultural worlds in which we live.
Hacking
Interacting with computers in playful and exploratory ways. Computers aren’t magic, as long as we keep in mind that humans are responsible for the creation of machines, and it’s programming, and that computers contain limitations.
put power in the hands of users: and de-centralizes control.
DIY
If you do not like the way things are done, then you should Do It Yourself!
References
- Critical Art Ensemble (http://critical-art.net/
- Jonah Brucker-Cohen My process embraces a playful approach to changing people’s notions of how networks and used and function.
- Lalya Gaye, sonic city
This file was generated using pandoc:
pandoc --from markdown --to mediawiki -o file.mediawiki {file}.md --template=/default.mediawiki