Waggish

David Auerbach on literature, tech, film, etc.

Tag: microsoft

Cultural Illogic: David Golumbia and The Cultural Logic of Computation

David Golumbia does not like computers. Toward the end of The Cultural Logic of Computation, after lumping computers and the atom bomb into a single “Pandora’s Box” of doom, he observes:

The Germans relied on early computers and computational methods provided by IBM and some of its predecessor companies to expedite their extermination program; while there is no doubt that genocide, racial and otherwise, can be carried out in the absence of computers, it is nevertheless provocative that one of our history’s most potent programs for genocide was also a locus for an intensification of computing power.

This sort of guilt by association is typical of The Cultural Logic of Computation. The book is so problematic and so wrong-headed as to be shocking, and as philosophical and cultural excursions into technological analysis are still comparatively rare, the book merits what programmers would term a postmortem.

Throughout the book, Golumbia, an English and Media Studies professor who worked for ten years as a product manager in software at Dow Jones, insists that computers are creating and enforcing a socio-political hegemony that reduces human beings to servile automatons. They aren’t just the tools of oppression, they oppress by their very nature. Golumbia attacks the encroachment by “computation” on human life. He defines “computation” as the rationalist, symbolic approach of computers and logic.

Or at least he seems to sometimes. Other times “computation” stands in for an amorphous mass of cultural issues that just happen to involve computers. Much of the the book focuses on political issues that don’t bear on “computation” in the least, such as a tired attack on Thomas Friedman and globalization that adds nothing new to Friedman’s already-long rap sheet. Golumbia spends ten pages criticizing real-time strategy games like Age of Empires, complaining:

There is no question of representing the Mongolian minority that exists in the non-Mongolian part of China, or of politically problematic minorities such as Tibetans and Uyghurs, or of the other non-Han Chinese minorities (e.g., Li, Yi, Miao).

A true Hobbesian Prince, the user of Age of Empires allows his subjects no interiority whatsoever, and has no sympathy for their blood sacrifices or their endless toil; the only sympathy is for the affairs of state, the accumulation of wealth and of property, and the growth of his or her power.

The critique could apply just as easily to Monopoly, Diplomacy, Stratego, or chess.

Golumbia gives away the game, so to speak, when he implies that connectionism (a non-symbolic artificial intelligence approach used in neural networks) is somehow less politically suspect than the symbolic AI approaches he attacks. In fact, non-symbolic approaches like Bayes networks and neural networks are themselves used ubiquitously in the data mining he (rightly) worries about. Golumbia has confused science with scientism, and computers’ uses with their structure.

Without a critique of the technical side of computers, Golumbia’s book would be just another tired retread of Chomsky, Hardt/Negri, Spivak, Thomas Frank, and the like. Unfortunately, his actual excursions into technical issues are woefully uninformed. A surreal attack on XML as a “top-down” standard ends with him praising Microsoft Word as an alternative, confusing platform and application. He hates object-oriented programming because…well, I’m honestly not quite sure.

Because the computer is so focused on “objective” reality—meaning the world of objects that can be precisely defined—it seemed a natural development for programmers to orient their tools exactly toward the manipulation of objects. Today, OOP is the dominant mode in programming, for reasons that have much more to do with engineering presumptions and ideologies than with computational efficiency (some OOP languages like Java have historically performed less well than other languages, but are preferred by engineers because of how closely they mirror the engineering idealization about how the world is put together).

The lack of citation, pervasive throughout the book, makes it impossible even to pinpoint what this objection means. I’d be curious as to how he feels about functional languages like Lisp, ML, and Haskell, but Golumbia shows no signs of even having heard of them. Unfortunately, XML and object-oriented programming are pretty much his two main points of technical attack, which indicates a lack of technical depth.

Yet Golumbia’s greatest anger is reserved for Noam Chomsky. Golumbia devotes a quarter of the book to him, with Jerry Fodor serving as assistant villain. Somehow, Chomsky’s computational linguistics become far more than just a synecdoche for modern corporatism and materialism; Chomsky is actually one of the main culprits.

To Golumbia, Chomsky is “fundamentally libertarian”; he is a Ayn Randian “primal conservative” who accepted military funding. He has “authoritarian” institutional politics which require strict adherence to his “religious” doctrine:

Chomsky’s institutional politics are often described exactly as authoritarian.

[His work] tends to attract white men (and also men from notably imperial cultures, such as those of Korea or Japan).

The scholars who pursue Chomskyanism and Chomsky himself with near-religious fervor are, almost without exception, straight white men who might be taken by nonlinguists to be ‘computer geeks.’

Golumbia is evidently fond of the ad hominem. Golumbia also associates “geeks” with “straight, white men,” insulting 19th century programmer Ada Lovelace, gay theoretician Alan Turing, and the vast population of queer and non-white programmers, linguists, and geeks that exists today (many not even Korean or Japanese).

Yet Golumbia finds time to praise Wikipedia, founded and run by fundamentally libertarian Ayn Rand acolyte Jimmy Wales. It’s strange for Golumbia to call Wikipedia a salutary effort to demote expert opinion when Wales himself says it should not be cited in academic papers. And strange for Golumbia to see Wikipedia as progressive when many of its entries still come from that well-known bastion of hegemonic opinion, the 1911 Encyclopedia Britannica. (The explicitly racist ones have been scrubbed.)

Beyond the technological confusions, Golumbia’s philosophical background is notably defective. The book is plagued by factual errors; Voltaire is bizarrely labeled a “counter-Enlightenment” thinker, while logicians Bertrand Russell and Gottlob Frege somehow end up on opposite sides: Russell is a good anti-rationalist (despite having written “Why I Am a Rationalist”), Frege is a bad rationalist. (He also enlists Quine and Wittgenstein to his leftist cause, which I suspect neither would have appreciated.) He thinks Leibniz preceded Descartes. He misappropriates Kant’s ideas of the noumenal and mere reason.

Here is a typically confused passage, revealing Golumbia’s fondness for incoherent Manicheistic dichotomies:

In Western intellectual history at its most overt, mechanist views typically cluster on one side of political history to which we have usually attached the term conservative. In some historical epochs it is clear who tends to endorse such views and who tends to emphasize other aspects of human existence in whatever the theoretical realm. There are strong intellectual and social associations between Hobbes’s theories and those of Machiavelli and Descartes, especially when seen from the state perspective. These philosophers and their views have often been invoked by conservative leaders at times of consolidation of power in iconic or imperial leaders, who will use such doctrines overtly as a policy base.

This contrasts with ascendant liberal power and its philosophy, whose conceptual and political tendencies follow different lines altogether: Hume, Kant, Nietzsche, Heidegger, Dewey, James, etc. These are two profoundly different views of what the State itself means, what the citizen’s engagement with the State is, and where State power itself arises. Resistance to the view that the mind is mechanical is often found in philosophers we associate with liberal or radical views—Locke, Hume, Nietzsche, Marx.

So it is not simply the technological material that is the problem. The quality of even the academic, philosophical portions of the book is dismaying, and the general lack of evidence and citation is egregious. Harvard University Press, who published the book, have a fine track record in the general areas that Golumbia inhabits. I am not certain how The Cultural Logic of Computation slipped through, nor how many of its blatant errors were not caught. It is an embarrassment and will only confirm the prejudices of those who feel that the humanities have nothing to offer the sciences but spite and ignorance.

For contrast, Samir Chopra’s Decoding Liberation: The Promise of Free and Open Source Software (Routledge) is an excellent and rigorous examination of some of the political and social issues around software and software development, strong on both the technical and philosophical fronts. I would urge anyone looking at Golumbia’s book to read it instead.

Profiles in Type L: Some Engineer at Microsoft

(Original typology in Battle Lines: Type L are the free-market technocrats and Type C are the conservative old boys in American society. Once more, I don’t identify with either of them.)

The always-intriguing corporate-insider blog Mini-Microsoft is the venting place for many of the R+D people dissatisfied with the state of affairs at that company. One anonymous commenter effectively summarizes the Type L’s case against the Type C, much as Paul Van Riper did. The parallels in content and attitude are very striking. I don’t get some of the terminology in the comment either, but this person’s point comes across anyway.

There are some geniuses over in Microsoft Research; somebody needs to set them free to productize.

It isn’t a lack of IC [individual contributor] talent. Although that is rapidly changing. it’s the decline of technical talent and integrity at almost all levels of management.

With “trios”, no individual is charged with cross-discipline technical oversight until GM or VP level. This is no the job of a GM or VP. It *was* the job of the now-extinct Product Unit Manager. Doubtless trios was sold as a way to commoditize skills by narrowing the remit of individuals along discipline lines. Unfortuately, those with broad skill sets that can envision how to actually make a prodcut (rather than a document or a nice report) have been pushed out. It is the age of the bureaucrat.

With trios, the notion of “product team” has vanished. A product team comprised all disciplines, and (usually) et weekly, with their PUM. This has been replaced by layers of tripartite committees based around the arbitrary notion of Dev, Test, PM. The meetings required have grown exponentially. A product team may only get together at a divisional all-hands.

BY GM/VP level, reporting on product state has been so sanitized that the majority of issues are never even surfaced. Yes, there is of course a category of issues that should never require a VPs intervention, but this goes way beyond that. “No bad news, ever”, is the rule. Anyone who rocks the boat is one of those negative, non-team-player 10%ers who will shortly be gone.

More senior ICs are, by definition, supposed to raise broad issues by dint of their level and years of experience. The existing culture makes this a very dangerous thing to do. That’s why I left in January after 10+ years.

The various disasters/missed opportunities over the last 10 years were well known to engineers at the front line… but due to a viciously-enforced policy of “no bad news, ever”, those who might have taken corrective action don’t find out until its too late.

There is a clear pattern of failure to execute… and it is not the doing of engineers. It’s a culture that rewards the suppression of “bad news”. It’s the lack of spine in the management chain to unpromise things that were promised, and blame their “underperforming” ICs when the crap hits the fan. Those with a spine soon find their prospects blighted.

Changing VPs won’t help much. They rely on their generals amd below to garner a picture of the situation. If those generals don’t provide truthful reporting, it simply isn’t possible to execute effectively. It’ll take an IBM/GE/HP/Honeywell (etc) sttyle intervention to fix this problem – it won’t get fixed by those who benefit (hugely) from it.

It’s like watching the third season of The Wire!

© 2019 Waggish

Theme by Anders NorenUp ↑