
Science in Action: How to Follow Scientists and Engineers Through Society is a seminal book by French philosopher, anthropologist and sociologist Bruno Latour first published in 1987. It is written in a textbook style, proposes an approach to the empirical study of science and technology, and is considered a canonical application of actor-network theory. It also entertains ontological conceptions and theoretical discussions making it a research monograph and not a methodological handbook per se.
MIT Press has a wide variety of books that cover specific topics in history, most of which have great theoretic interest: Agar's "The Government Machine," dealing with the evolution of technology and expertise within the UK government; Medina's "Cybernetic Revolutionaries," about Beer's Cybersyn project; and Ensmenger's "The Computer Boys Take Over," about the cultural development of the "programmer," are all great reads.
Also, you can look beyond pure technology for interesting adjacencies: for example, Schatz's "The Genius of the System" describes how changes in technology and management production radically upended Hollywood, resulting in the studio system that dominated from the 1930s through the 1950s, while Harris' "Pictures at a Revolution" picks up the pieces at the end of that system, discussing the rise of "New Hollywood," driven by cultural and technical (particularly the French use of inexpensive filming technologies to create the New Wave) forces.
I found the book super interesting in terms of explaining how innovations happen and how we talk about them in retrospect. Although it is about science, I think a lot of the thinking would apply to programming innovations too. And unlike most blog posts, there is actually some serious sociological research behind it :-).
Therefore, to some programmers, if someone else is likely to do something more brilliant than you, it's motivating to stop them. Especially so, since if you are successful in stopping them, your own perceived merit goes up as the smarter dog in the room.
This game is reinforced by the game of karma on many programmer discussion sites. I have to admit, I succomb, as I want my karma to cross 200 so I can downvote. It's a stupid goal, but my ego is prone to it.
P.S. Please note that science is also prone to this behaviour, and programming and science have the same solution to the problem: actually building a verifiable { experiment / correct theorem / more efficient algorithm }.
cf. Science in Action by Bruno Latour (1987), which I tried to summarize on http://www.usemod.com/cgi-bin/mb.pl?SocialConstructionOfScie...
> Since the settlement of a controversy is the cause of Nature's representation, not its consequence, we can never use this consequence, Nature, to explain how and why a controversy has been settled. (Science in Action)
Bruno Latour was among the selected few that were criticized in Sokal and Bricmont's "Fashionable Nonsense: Postmodern Intellectuals' Abuse of Science".
https://en.wikipedia.org/wiki/Sokal_affair
http://www.physics.nyu.edu/faculty/sokal/transgress_v2/trans...
