Goodreads helps you follow your favorite authors. Be the first to learn about new releases!
Start by following Janet Abbate.
Showing 1-5 of 5
“The story of the Internet's origins departs from the explanations of technical innovation that center on individual inventors or on the pull of markets. Cerf and Kahn were neither captains of industry nor "two guys tinkering in a garage." The Internet was not built in response to popular demand, real or imagined; its subsequent mass appeal had no part in the decisions made in 1973. Rather, the project reflected the command economy of military procurement, where specialized performance is everything and money is no object, and the research ethos of the university, where experimental interest and technical elegance take precedence over commercial application. This was surely an unlikely context for the creation of what would become a popular and profitable service. Perhaps the key to the Internet's later commercial success was that the project internalized the competitive forces of the market by bringing representatives of diverse interest groups together and allowing them to argue through design issues. Ironically, this unconventional approach produced a system that proved to have more appeal for potential "customers"—people building networks—than did the overtly commercial alternatives that appeared soon after.”
― Inventing the Internet
― Inventing the Internet
“As to the future, the only certainty is that the Internet will encounter new technical and social challenges. If the Internet is to continue as an innovative means of collaboration, discovery, and social interaction, it will need to draw on its legacy of adaptability and participatory design.”
― Inventing the Internet
― Inventing the Internet
“The early history of programming methods shows how seemingly technical debates can encode social issues such as labor and gender. The assumption that programming would be improved by making it more like engineering was based on the cultural linking of engineering with masculinity and, by extension, with prestige and authority. Rethinking the gendered value system that is embedded in the metaphor of engineering—perhaps by reclaiming women’s understandings of the term—has the potential not only to make computer science and programming more appealing to women but also to benefit the discipline itself.”
― [Recoding Gender: Women's Changing Participation in Computing (History of Computing)] [By: Abbate, Janet] [October, 2012]
― [Recoding Gender: Women's Changing Participation in Computing (History of Computing)] [By: Abbate, Janet] [October, 2012]
“A 1964 study illustrated how status considerations could distort people's perceptions of the level of skill that was involved in various programming jobs. The study asked experienced computer personnel to distribute a list of programming tasks among a hierarchy of jobs–systems analyst, senior programmer, and programmer. The author found that "the higher the level of the job, the more job skills were included"–even if some of those tasks normally were performed by workers in the lower-status jobs. Higher-status workers were simply assumed to have a monopoly on skilled tasks, even by people who were familiar with the field and should have known better. We should not be surprised to find that employers, who often had no personal knowledge of programming, fell back on social categories when evaluating potential workers.”
― Recoding Gender: Women's Changing Participation in Computing
― Recoding Gender: Women's Changing Participation in Computing
“Another detrimental effect of undervaluing people skills was that in some cases, programmers were rewarded more for raw code production than for meeting the user's needs. Marge Devaney, a programmer at Los Alamos National Laboratory in the 1950's, recalled sex differences in how programmers judged their performance. Asked if she had ever experienced gender bias on the job, sh replied that discrimination was difficult to prove, adding, "With things like computing, it's very hard to judge who's doing the best. Is it better to produce a program quickly and have it full of bugs that the users keep hitting, and so it doesn't work? Or is it better to produce it more slowly and have it so it works?...I do know some of the men believed in the first way: 'Throw it together and let the user debug it!'" This critique is echoed by women today who find their male peers rewarded for averting disasters through heroic last-minute efforts, while women's efforts at preventing such problems through careful work and communication with users go unrecognized. As a female software engineer complained in 2007, "Why don't we just build the system right in the first place? Women are much better at preventive medicine. A Superman mentality is not necessarily productive; it's just an easy fit for the men in the sector.”
― Recoding Gender: Women's Changing Participation in Computing
― Recoding Gender: Women's Changing Participation in Computing




