My book, Programmed Inequality: How Britain Discarded Women Technologists and Lost Its Edge In Computing, published by MIT Press, has been awarded the 2019 Herbert Baxter Adams Prize from the American Historical Association. (It also won the 2018 PROSE Award for History of Science, Technology, and Medicine from the Association of American Publishers; The 2018 Sally Hacker Prize from the Society for the History of Technology; The 2018 Stansky Prize from the North American Conference on British Studies; and the 2018 Wadsworth Prize from the British Business Archives Council.)
The short guide below evolved out of a conversation with Miriam Posner (@miriamkp) of UCLA who was looking for ways to help her students read more quickly and effectively. These tips can help you retain more when reading academic texts and allow you to get through them at a quicker pace.
Here’s what I tell my students if they have trouble keeping up with the reading for my history and STS classes: Continue reading
This year, at the University of Madison-Wisconsin, I am teaching a new and improved version of my popular course Women in Computing History. It was initally taught at Illinois Tech in Chicago last year, where it garnered some press attention.
Due to the interest the course generated with people beyond the walls of our classroom I annotated the syllabus with discussion topics and class notes to give a sense of what we did in each class meeting–and what kinds of questions might be useful if you do the readings on your own.
See my syllabus page for the newest version of the course–the old version is still available as well, for all you completionists who might want to look at the details of how the course has changed!
I recently wrote a piece for the Washington Post using history to debunk the infamous “Google Memo” and its contention that women are somehow less innately suited to technical pursuits. Truth is, for a long time women were predominant in the field of computing because technical work wasn’t seen as important. Their disappearance has everything to do with structural discrimination and little to do with “innate” differences.
I was also very glad to get a few mentions in The Guardian. See this (delightfully acerbic) article about memogate in general, and this one that’s specifically about the history of computing’s role in helping us better understand power and (the lack of) diversity in our technological landscape in the present.
Quick note about the latter article–it made a little bit of a mistake in the first few lines (read more here and here). Both SUSIE and SADIE were computers. The typist/programmer in the ad was unnamed.
Five years ago, Silicon Valley was rocked by a wave of “brogrammer” bad behavior, when overfunded, highly entitled, mostly white and male startup founders did things that were juvenile, out of line and just plain stupid. Most of these activities – such as putting pornography into PowerPoint slides – revolved around the explicit or implied devaluation and harassment of women and the assumption that heterosexual men’s privilege could or should define the workplace. The recent “memo” scandal out of Google shows how far we have yet to go.
Recently I gave a talk at Data & Society, a think tank in NYC that focuses on issues of social justice and technology. The talk was about how the history of computing of our closest historical cousin, the UK, can help us learn things about the past and present of the US–things that we may be blind to, or perhaps just resistant to seeing. The half-hour talk is an overview of what happens when countries build discrimination into technological order, rather than seeking to make equality a core goal of technological progress. In it, I address how the current state of affairs in the US relates to this, and I offer some advice on solving the problems of underrepresentation in STEM fields today. Watch the talk here.