Welcome to Bookmarker!

This is a personal project by @dellsystem. I built this to help me retain information from the books I'm reading.

Source code on GitHub (MIT license).

69

Big Diff, granularity, incoherence and production in the Github software repository

0
terms
3
notes

with Andrew Goffey, Adrian Mackenzie, Richard Mills and Stuart Sharples

Fuller, M. (2017). Big Diff, granularity, incoherence and production in the Github software repository. In Fuller, M. How to Be a Geek: Essays on the Culture of Software. Polity Press, pp. 69-85

76

Amongst others, Philip Mirowski interprets neoliberal economics, particularly in the work of Friedrich Hayek, as the dream or ruse of a perfect information machine. There are certainly accounts of distributed version control systems that have such an inflection, or make the explicit correlation with idealized markets. [...]

this definitely feels like a leap but maybe they're onto something here, idk

—p.76 by Matthew Fuller 10 months, 1 week ago

Amongst others, Philip Mirowski interprets neoliberal economics, particularly in the work of Friedrich Hayek, as the dream or ruse of a perfect information machine. There are certainly accounts of distributed version control systems that have such an inflection, or make the explicit correlation with idealized markets. [...]

this definitely feels like a leap but maybe they're onto something here, idk

—p.76 by Matthew Fuller 10 months, 1 week ago
78

[...] Github works via the encouragement of contribution. Some of this encouragement is achieved through an efficient and useful system, via the extension adoption of user experience design, contemporary 'flat design'-style graphic design and, of course, a cartoon mascot. Equally, the site operates by numerous types of granularity of access to analytics. There are numerous 'social' features such as letting you view the repos 'people you may know' have starred [...] we have the archive also operating as a matrix of capture and semiotization devices driven by the imperatives to rate, share, participate! As an economic factor, such hyper-auditing devices allow the site to become a means of finding an hiring programmers; Git and Github profiles become key to coders' CVs as a means of displaying the productivity, uptake and significance of the work produced. In this way, as in others, the archive is a site of production, an engine for the development of new software that involutes the sense or the archive as a repository of the unchanging past. Storage becomes the site of production when the form of production is variation.

need to think about insightful the last bit really is, but it is cool to read about GitHub from this kind of theoretical perspective

—p.78 by Matthew Fuller 10 months, 1 week ago

[...] Github works via the encouragement of contribution. Some of this encouragement is achieved through an efficient and useful system, via the extension adoption of user experience design, contemporary 'flat design'-style graphic design and, of course, a cartoon mascot. Equally, the site operates by numerous types of granularity of access to analytics. There are numerous 'social' features such as letting you view the repos 'people you may know' have starred [...] we have the archive also operating as a matrix of capture and semiotization devices driven by the imperatives to rate, share, participate! As an economic factor, such hyper-auditing devices allow the site to become a means of finding an hiring programmers; Git and Github profiles become key to coders' CVs as a means of displaying the productivity, uptake and significance of the work produced. In this way, as in others, the archive is a site of production, an engine for the development of new software that involutes the sense or the archive as a repository of the unchanging past. Storage becomes the site of production when the form of production is variation.

need to think about insightful the last bit really is, but it is cool to read about GitHub from this kind of theoretical perspective

—p.78 by Matthew Fuller 10 months, 1 week ago
80

[...] Post-FLOSS inhabits conditions in which code objects, scripts, css files for the layout of a website, configuration files for customising the look and function of a program etc. form so much part of everyday generic stuff that they are not worth protecting in the way that the adoption of a licence implies, even when that licence is available on a drop-down menu.

—p.80 by Matthew Fuller 10 months, 1 week ago

[...] Post-FLOSS inhabits conditions in which code objects, scripts, css files for the layout of a website, configuration files for customising the look and function of a program etc. form so much part of everyday generic stuff that they are not worth protecting in the way that the adoption of a licence implies, even when that licence is available on a drop-down menu.

—p.80 by Matthew Fuller 10 months, 1 week ago