February 2022 - Members - lists.sigcis.org

Moore’s Not Enough: 4 New Laws of Computing
by Joly MacFie 14 Feb '22

14 Feb '22

[I thought this worthy of circulation - Joly] https://spectrum.ieee.org/on-beyond-moores-law-4-new-laws-of-computing *Moore’s Not Enough: 4 New Laws of Computing * *Moore’s and Metcalfe’s conjectures are taught in classrooms every day—these four deserve consideration, too * *ADENEKAN DEDEKE * *04 FEB 2022* I teach technology and information-systems courses at Northeastern University, <https://damore-mckim.northeastern.edu/people/adenekan-dedeke/> in Boston. The two most popular laws that we teach there—and, one presumes, in most other academic departments that offer these subjects—are Moore’s Law and Metcalfe’s Law. Moore’s Law, as everyone by now knows, predicts that the number of transistors on a chip will double every two years. One of the practical values of Intel cofounder Gordon Moore’s legendary law <https://en.wikipedia.org/wiki/Moore%27s_law> is that it enables managers and professionals to determine how long they should keep their computers. It also helps software developers to anticipate, broadly speaking, how much bigger their software releases should be. Metcalfe’s Law is similar to Moore’s Law in that it also enables one to predict the direction of growth for a phenomenon. Based on the observations and analysis of Robert Metcalfe <https://en.wikipedia.org/wiki/Robert_Metcalfe/>, co-inventor of the Ethernet and pioneering innovator in the early days of the Internet, he postulated that the value of a network would grow proportionately to the number of its users squared. A limitation of this law is that a network’s value is difficult to quantify. Furthermore, it is unclear that the growth rate of every network value changes quadratically at the power of two. Nevertheless, this law as well as Moore’s Law remain a centerpiece in both the IT industry and academic computer-science research. Both provide tremendous power to explain and predict behaviors of some seemingly incomprehensible systems and phenomena in the sometimes inscrutable information-technology world. I contend, moreover, that there are still other regularities in the field of computing that could also be formulated in a fashion similar to that of Moore’s and Metcalfe’s relationships. I would like to propose four such laws. *Law 1. Yule’s Law of Complementarity* I named this law after George Udny Yule <https://en.wikipedia.org/wiki/Udny_Yule> (1912), who was the statistician who proposed the seminal equation <https://en.wikipedia.org/wiki/Yule%E2%80%93Simon_distribution> for explaining the relationship between two attributes. I formulate this law as follows: *If two attributes or products are complements, the value/demand of one of > the complements will be inversely related to the price of the other > complement.* In other words, if the price of one complement is reduced, the demand for the other will increase. There are a few historical examples of this law. One of the famous ones is the marketing of razor blades. The legendary King Camp Gillette <https://en.wikipedia.org/wiki/King_C._Gillette> gained market domination by applying this rule. He reduced the price of the razors, and the demand for razor blades increased. The history of IT contains numerous examples of this phenomenon, too. The case of Atari 2600 is one notable example. Atari video games consisted of the console system hardware and the read-only memory cartridges that contained a game’s software. When the product was released, Atari Inc. marketed three products, namely the Atari Video Computer System <https://spectrum.ieee.org/atari-2600> (VCS) hardware and the two games that it had created, the arcade shooter game *Jet Fighter* and *Tank*, a heavy-artillery combat title involving, not surprisingly, tanks. Crucially, Atari engineers decided that they would use a microchip for the VCS instead of a custom chip. They also made sure that any programmer hoping to create a new game for the VCS would be able to access and use all the inner workings of the system’s hardware. And that was exactly what happened. In other words, the designers reduced the barriers and the cost necessary for other players to develop VCS game cartridges. More than 200 such games have since been developed for the VCS—helping to spawn the sprawling US $170 billion global video game industry today <https://www.mordorintelligence.com/industry-reports/global-gaming-market>. A similar law of complementarity exists with computer printers. The more affordable the price of a printer is kept, the higher the demand for that printer’s ink cartridges. Managing complementary components well was also crucial to Apple’s winning the MP3 player wars of the early 2000s <https://books.google.com/books?id=tGUYDQAAQBAJ&q=ipod#v=snippet&q=ipod&f=fa…>, with its now-iconic iPod. >From a strategic point of view, technology firms ultimately need to know which complementary element of their product to sell at a low price—and which complement to sell at a higher price. And, as the economist Bharat Anand points out in his celebrated 2016 book <https://books.google.com/books?id=tGUYDQAAQBAJ&vq=ipod&source=gbs_navlinks_s>*The Content Tra <https://books.google.com/books?id=tGUYDQAAQBAJ&vq=ipod&source=gbs_navlinks_s>p*, proprietary complements tend to be more profitable than nonproprietary ones. *Law 2. Hoff’s Law of Scalability* This law is named after Marcian Edward (Ted) Hoff Jr.—the engineer who convinced the CEO of Intel to apply the law of scalability to the design and development of processors. Certainly, the phenomenon of scalability was well known in the automobile industry before it made a significant impact on the computing industry. Henry Ford was a notable example of the application of this scalability law. Henry Ford’s company was perhaps the first company to apply this law on a grand scale. Ford produced the Model T, which was the first mass-produced car. At the core of Henry Ford’s achievement was the design of an automobile that was made for mass production. Ford’s engineers broke down the assembly process of the Model T into 84 discrete steps <https://www.mlive.com/news/detroit/2018/01/historic_photos_fords_assembly.h….>. The company standardized all the tasks and assigned each worker to do just one task, thus standardizing the work each worker performed as well. Ford further built machines that could stamp out parts automatically. Together with Ford’s innovative development of the first moving assembly line, this production system cut the time to build a car from 12 hours to about 1.5 hours <https://www.history.com/this-day-in-history/fords-assembly-line-starts-roll…>. The Model T is probably the paradigmatic example of how standardization enables designing processes for scalability. Intel also mastered the law of scalability early in its history. In 1969, Busicom, a Japanese company, approached Intel about building custom chips <https://spectrum.ieee.org/chip-hall-of-fame-intel-4004-microprocessor> for use in its programmable computers. Gordon Moore was not interested in a custom chip because he knew that it would not be scalable. It was the quest to create a scalable product that led Intel’s Ted Hoff to partition the chip into a general-purpose logic processor chip and a separate read-only memory (ROM) chip that stored an application program. As Albert Yu shows in his history of Intel, *Creating the Digital Future <https://books.google.com/books/about/Creating_the_Digital_Future.html?id=AY…>*, the fledgling semiconductor company’s general-purpose processor, the 4004, was scalable and pretty much bequeathed the world the hardware architecture of the modern computer. And it was Hoff who redesigned the 4004 to scale. Hoff’s Law of Scalability could thus be described as follows: *The potential for scalability of a technology product is inversely proportional to its degree of customization and directly proportional to its degree of standardization.* In sum, the law predicts that a technology component or process that has a high degree of customization and/or a lower degree of standardization will be a poor candidate for scaling. *Law 3. Evans’s Law of Modularity* This law derives its name from Bob Overton Evans <https://en.wikipedia.org/wiki/Bob_O._Evans>. He was the engineer who in the early 1960s persuaded IBM’s chairman, Thomas J. Watson Jr <https://en.wikipedia.org/wiki/Thomas_J._Watson>., to discontinue IBM’s technology design approach, which had produced a hodgepodge of incompatible computers. Evans advocated that IBM should instead embark on the development of a family of modular computers that would share peripheries, instructions, and common interfaces. IBM’s first product family under this new design rubric was called System/360 <https://en.wikipedia.org/wiki/IBM_System/360>. Prior to this era, IBM and other mainframe computer manufacturers produced systems that were unique. Each system had its own distinct operating system, processor, peripherals, and application software. After the purchase of a new IBM computer, customers had to rewrite all their existing code. Evans convinced CEO Watson that a line of computers should be designed to share many of the same instructions and interfaces. This new approach of modular design meant that IBM’s engineers developed a common architecture (the specification of which functions and modules will be part of the system), common interfaces (a description of how the modules will interact, fit together, connect, and communicate), and common standards (a definition of shared rules and methods that would be used to achieve common functions and tasks). This bold move on Big Blue’s part created a new family of computers that revolutionized the computer industry. Customers could now protect their investments because the instructions, software, and peripheries were reusable and compatible within each computer family. Evans’s Law could be formulated as follows: *The inflexibilities, incompatibilities, and rigidities of complex and/or > monolithically structured technologies could be simplified by the > modularization of the technology structures (and processes).* This law predicts that the application of modularization will reduce incompatibilities and complexities. One further example of Evans’s Law can be seen in the software development industry, as it has shifted from the “waterfall” to the agile software development methodology <https://www.forbes.com/advisor/business/agile-vs-waterfall-methodology/>. The former is a linear and sequential model stipulating that each project phase can begin only the previous phase has ended. (The name comes from the fact that water flows in only one direction down a waterfall.) By contrast, the agile development approach applies the law of modularization to software design and the software development process. Agile software developments tend to be more flexible, more responsive, and faster. In other words, modularization of software projects and the development process makes such endeavors more efficient. As outlined in a helpful 2016 *Harvard Business Review* <https://hbr.org/2016/05/embracing-agile> article, the preconditions for an agile methodology are as follows: The problem to be solved is complex; the solutions are initially unknown, with product requirements evolving; the work can be modularized; and close collaboration with end users is feasible. *Law 4. The Law of Digitiplication* The concept of digitiplication is derived from two concepts: digitalization and multiplication. The law stems from my own study and observations of what happens when a resource is digitized or a process is digitalized. *The law of digitiplication stipulates that whenever a resource or process > is digitalized, its potential value grows in a multiplicative manner.* For example, if a paper is copied four times, one can now share the resource with five people. But digitize the document and the value-creation opportunities are multiplicative rather than additive. Consider the example of a retail store. The store’s sales reps, tasked with selling physical products to individual people, are able to service only one customer at a time. However, if the same retail environment is placed online, many customers can view the store’s products and services. Digital text can also easily be transformed into an audio format, providing a different kind of value to customers. Search functionality within the store’s inventory of course adds another layer of value to the customer. The store’s managers can also monitor how many customers are viewing the store’s website’s pages and for how long. All of these enhancements to the customer’s (and retailer’s) experience provide different kinds of value. As can be seen by these examples, the digitalization of a resource, asset, or process creates multiplicative rather than additive value. As a further example, Amazon founder Jeff Bezos first began digitizing data about books as a way to facilitate more and greater book sales online. Bezos quickly transformed Amazon into a digitiplication engine by becoming a data-centric e-commerce company. The company now benefits from the multiplicative effects of digitalized processes and digitized information. Amazon’s search, selection, and purchase functions also allow the company to record and produce data that can be leveraged to predict what the customer wants to buy—and thus select which products it should show to customers. The digitization of customer feedback, seller ratings, and seller feedback creates its own dimension of multiplicative value. Conclusion These four laws can be useful for engineers and designers to pose questions as they begin to develop a product. For example: Do customer requirements lend themselves to a product design that could be scaled (or mass-produced)? Might the functional requirements they’re working with be satisfied through the development of a modular product design? Could Yule’s Law of Complementarity provide cues toward mass production or modular design alternatives? Could product complements be developed in-house or outsourced? Software engineers might also be led toward productive questions about how data could be digitized, or how specific processes could be digitalized to leverage the law of digitiplication. The fields of IT and electrical engineering and computer science (EECS) have become critical disciplines of the digital age. To pass along the most succinct and relevant formulations of accumulated knowledge to date to the next generation, it's incumbent on academics and thought leaders in these essential technical fields to translate lessons learned into more formalized sets of theorems and laws. Such formulations would, I hope, enable current and future generations of IT and EECS professionals to develop the most useful, relevant, impactful, and indeed sometimes even disruptive technologies. I hope that the proposed four laws in this article could help to trigger a larger discussion about the need for and relevance of new laws for our disciplines. -- -------------------------------------- Joly MacFie +12185659365 -------------------------------------- -

2 1

Toward Cognitive Search: Using Machine-Learning on Digital Media Collections
by Hansen Hsu 11 Feb '22

11 Feb '22

Hi everyone, CHM is hosting a virtual event next Friday, Feb 18, to show our findings from a pilot project to use machine learning on our collections, funded by a grant from the Moore Foundation. I thought you might be interested in this. https://computerhistory.org/events/toward-cognitive-search/#register .................................... Hansen Hsu, Ph.D. Curator, Software History Center Computer History Museum<http://www.computerhistory.org/> 1401 N. Shoreline Blvd. Mountain View, CA 94043 (650) 810-1880 direct (650) 810-1010 main (650) 284-6254 mobile (650) 810-1055 fax hhsu(a)computerhistory.org<mailto:hhsu@computerhistory.org> Follow Us: CHM Blog<http://www.computerhistory.org/atchm/> I Facebook<http://www.facebook.com/computerhistory> I Twitter<http://www.twitter.com/computerhistory> I YouTube<http://www.youtube.com/computerhistory>

1 0

Come and party with early graphics geeks
by LO*OP CENTER, INC. 10 Feb '22

10 Feb '22

The Graphics Gathering celebrates its 42 Birthday with a cool online party on two separate days: 20 Feb & 22 Feb. First day will focus on computing and computer graphics. Second day will be more about climate change and political action. http://ecocre8.com for more details. -- Liza Loop Executive Director, LO*OP Center, Inc. Guerneville, CA 95446 www.loopcenter.org 650 619 1099 (between 8 am and 10 pm Pacific time only please)

1 0

Shiva Ayyadurai - he's making money "auditing" elections
by Jonathan Coopersmith 09 Feb '22

09 Feb '22

https://www.thedailybeast.com/pro-trump-otero-county-in-new-mexico-is-carry… Stay sane and get a booster (partially for you; more for others), Jonathan Jonathan Coopersmith Professor Department of History Texas A&M University College Station, TX 77843-4236 979.739.4708 (cell) 979.862.4314 (fax) America's "stab in the back"myth: https://theeagle.com/opinion/columnists/unnerving-similarities-to-jan-6/art… Preserving space archives: https://www.toboldlypreserve.space/ International standards battles: https://spectrum.ieee.org/tech-talk/geek-life/history/lets-thwart-this-terr… <https://urldefense.com/v3/__https://spectrum.ieee.org/tech-talk/geek-life/h…> *FAXED. The Rise and Fall of the Fax Machine* (Johns Hopkins University Press)

1 0

How did the Incas calculate with yupanas?
by herbert.bruderer＠bluewin.ch 06 Feb '22

06 Feb '22

Dear colleagues: The Romans used the abacus for calculations and recorded the results with Roman numerals. The Incas recorded the values with quipus and calculated with yupanas. Does anyone know how they calculated with these tools? Many thanks. Best wishes, Herbert Bruderer -- Bruderer Informatik Seehaldenstrasse 26 Postfach 47 CH-9401 Rorschach Switzerland Telefon +41 71 855 77 11 Bruderer, Herbert [2020a]: Milestones in Analog and Digital Computing, Springer Nature Switzerland AG, Cham, 3rd edition 2020, 2 volumes, 2113 pages, 715 illustrations, 151 tables, https://www.springer.com/de/book/9783030409739 Bruderer, Herbert [2020b]: Meilensteine der Rechentechnik, De Gruyter Oldenbourg, Berlin/Boston, 3. Auflage 2020, Band 1, 970 Seiten, 577 Abbildungen, 114 Tabellen, https://www.degruyter.com/view/title/567028?rskey=xoRERF&result=7 Bruderer, Herbert [2020c]: Meilensteine der Rechentechnik, De Gruyter Oldenbourg, Berlin/Boston, 3. Auflage 2020, Band 2, 1055 Seiten, 138 Abbildungen, 37 Tabellen, https://www.degruyter.com/view/title/567221?rskey=A8Y4Gb&result=4

2 1

Search for new EIC for IEEE Annals of the History of Computing
by William Aspray 05 Feb '22

05 Feb '22

The IEEE Annals of the History of Computing has been a central part of the history of computing community since the 1970s. The IEEE Computer Society is now searching for a new editor-in-chief for Annals, for a three-year term beginning 1 January 2023. (An EIC can apply later for a second term of two years.) For more information about the Computer Society and Annals, and to learn about the application process, see https://www.computer.org/press-room/2021-news/ieee-cs-pubs-seek-2023-editor… <https://www.computer.org/press-room/2021-news/ieee-cs-pubs-seek-2023-editor…>. Please note that the deadline for receipt of applications is 1 March 2022. If you have other questions about the EIC position, please feel free to contact me as nominations committee chair at william.aspray(a)icloud.com.

1 0

CACM piece on A New History of Modern Computing/Sinclair QL up next
by thomas.haigh＠gmail.com 04 Feb '22

04 Feb '22

Dear SIGCIS, Anyone curious about A New History of Modern Computing (MIT Press, 2021) which I wrote with Paul Ceruzzi, but not curious enough to have actually read the book, might be interested in my latest to the February issue of Communications of the ACM. "Becoming Universal: A New History of Modern Computing" looks at some of the special challenges of writing an overview history of a technology as mutable as the computer, talks about some of our decisions and key themes, and gives an idea of how the book differs from earlier overview histories. You can read it at https://cacm.acm.org/magazines/2022/2/258223-becoming-universal/fulltext My next contribution will be a delayed reaction to the death of Clive Sinclair, focused on the machine that his obituaries tended to overlook: the Sinclair QL. If any of you have QL stories to share, let me know. Also, if anyone has contact information for Tony Tebby, David Karlin, or Jan Jones I'd be interested to get it. If you haven't heard of the QL but like reading about 1980s computer platforms, take a look at https://www.theregister.com/2014/01/12/archaeologic_sinclair_ql/ for the story. Also chapter 8 of Adamson and Kennedy's book Sinclair and the 'Sunrise' Technology which is available at https://www.readanybook.com/online/681933. Best wishes, Tom

1 0

CfP: After Post-Photography 7 (June 2-4, 2022, St Petersburg // online)
by Dr. Friedrich Tietjen 03 Feb '22

03 Feb '22

Dear Sigcis, please see below the CfP for our next After Post-Photography conference in St Petersburg. Maria Gourieva and I started the conference series in 2015 and since then enjoyed the annual conferences quite a bit as did the (mostly) Russian audience - in particular because the open call attracted speakers from a wide variety of disciplines. So if you're doing research that one way or the other involves photography, feel welcome to submit a paper. Personally, I would be very interested in particular in papers on techno-racism (you probably remember the infamous HP-camera that would only recognize and track the movement of Caucasian faces) and on image generation in digital cameras (to name but a few subjects). Feel free to spread the word, and thanks for that Friedrich Stiftung Reinbeckhallen Berlin https://en.stiftung-reinbeckhallen.de/ https://univie.academia.edu/FriedrichTietjen ---snip--- After Post-Photography 7 - Presence and Absence International conference on visual studies, history and theory of photography 2-4 June 2022 European University (St. Petersburg, Russia // online) Maybe we never depended on photographic media as much as we do since early 2020. Probably we never looked so often, on so many occasions and at so many photographic images, as when wave after pandemic wave crashed into the world as we knew it. The less we could physically interact, the more we did by means of visual media. Instead of traveling we watched documentaries and were comforted a bit when videos showed a pair of dolphins swimming through Venice‘s Canale Grande where these animals had been absent for ages. We perused old family albums or sifted through the thousands of pictures on our hard drives. As libraries were closed, generous colleagues would snap page after page of book chapters someone else in the world was desperate to read. Our seminars were replaced by screens from which the participants‘ faces stared frontally, each one an involuntary panoptic jailer and inmate. And the breakout rooms of conferences were hardly a surrogate for the drafty hallways where gossip was exchanged and wild new research ideas developed over lukewarm coffee. The pandemic drama found its visual metaphors and allegories in the photograph of an Italian nurse collapsing after too many shifts, a short video of the former German tennis star Boris Becker applauding care workers from the balcony of his luxury mansion and demonstrations against the pandemic, lockdowns, vaccinations and the state as such. And as usual, many of its aspects remained invisible – the rise of domestic violence and alcoholism, the boring routine work in hospitals, the terrors of proximity in overcrowded camps, the dying in squalor of which there was rather more than less. In these and many more respects, a multitude of medialized relations of presence and absence and photography or – on broader terms – of visibility were negotiated within the framework of the pandemic. But of course these relations did not only emerge through the pandemic alone. In fact they are at the very core of images in general, and of photographs in particular. As photographic media shape our understanding of the world outside our immediate vicinity, their practices and politics of presence and absence are fundamental to modernity and its societies. Both practices and politics obviously depend upon what the images show. But in equal measure they also depend on how images are produced, distributed and reach out to their audiences. Thus, photographic presence and absence can happen in a lot of different ways. Photographic images can be applied to highlight, generate, select and obscure persons, objects, events and relations; they can render them special, ordinary, normal or boring. They can address individuals or everybody, they can aim for eternity or ephemerality. How all this was, is, or can be done depends not only on intentions but also on the technologies of the photographic media in question. These technologies however are neither objective nor are they neutral. How they cast the visibile - and invisible - into photograpic images depends upon the common politics and practices of visibility: if a team of engineers developes a facial recognition systems and trains it with portraits of predominantly white men, it is hardly surprising that it fails to identify or even recognize non-white persons. Under these conditions, possible topics include, but are not limited to - The image is the real thing: Photographic replacements - Skype, Zoom and BBB: Visual telepresence and other panoptical experiences - This can't be me: Non-representation through photography - Mobile presence: The smartphone as representation of the self - Photographic decay: What do faded photographs tell? - Technical blindness - what photography can't see or show - Photographic media and their audiences - You'll only see this once: Technical ephemerality - Photographs of what never has been: Retouching, rendering and other technologies of photo-realism - Pseudo-photography: The photographic aesthetics of sonographs, tomographs and other imaging methods As it was the case with previous conferences however, After Post-Photography is driven by a general curiosity in subjects of photography. Thus, there is only ground rule for submitting a paper to After Post-Photography: If you‘re doing Sociology, Nuclear Physics, Ethnology, Computer Sciences, Gender Studies, Meteorology, Law, Memory Studies, Criminology, Architecture, Archaeology, Botany, Art History, Mathematics, Numismatics, Astronomy, Game Studies, Oenology, Art History or any other discipline from science and humanities and your research involves photography in the broadest sense, we are happy to receive your paper. Please submit your application, including a short summary of your paper (250-400 words) only in English no later than February 28, 2022. Use the following link: https://easychair.org/conferences/?conf=app7; do not send submissions per eMail. Note that you need to register at the Easychair website in order to submit your application. Should you like to get in touch with us prior to your submission, please write to app(a)mur.at; we will get back to you within two or three days and if need be are also happy to talk to you via Zoom or Skype. There is no participation fee for the conference, neither for speakers nor for guests; should you like to support the conference however, let us know. As the pandemic continues, traveling options are impossible to predict which is why we plan for a hybrid conference. If your paper is accepted and you would like to come to St. Petersburg we regret that we can’t sponsor traveling or accommodation but can help you finding a place to stay. We will also provide you with an invitation in case you need a visa. The working languages of the conference are Russian and English, and during the conference, both papers and discussions will be translated. For programs of After Post-Photography conferences since 2015, please see www.after-post.photography We would sincerely appreciate it if you would circulate the call to your own networks and other mailing lists. Organizing committee After Post Photography 7 Olga Annanurova, Maria Gourieva, Olga Davydova, Natalia Mazour, Daria Panaiotti, Friedrich Tietjen

1 0

Venues for technical history?
by Jeffrey Starr 03 Feb '22

03 Feb '22

I'm interested in writing on technical computer science history topics (e.g. programming language history) and I'm trying to identify venues for short-form/article length publications. The focus would be on the engineering decisions and impact, rather than the social or business impact, which I understand is "out of scope" for many of the typical historical journals. Does this community have any recommendations? Jeffrey Starr

4 3

Re: [SIGCIS-Members] History of Computing/Technology podcasts?
by Shreeharsh Kelkar 02 Feb '22

02 Feb '22

Hi Ted, and all, Thanks for the links to those podcasts. Some of the podcasts I've listened to occasionally (and found quite good) on computing history are: Brian McCullough's Internet history podcast: http://www.internethistorypodcast.com/podcasts-by-chapter/. I don't think he publishes it anymore but I've liked quite a few of the episodes (I haven't listened to all of them by any means), especially some of the interviews with practitioners (e.g. with the people who brought the NYT and WSJ online). Gabriella Coleman's The Hackers podcast. https://www.bbc.co.uk/sounds/brand/m0012fjk Land of the Giants (these are histories of the giant internet companies) is a good series though it's about the last 20 years or so mostly. https://www.vox.com/land-of-the-giants-podcast. They also had this one-off season on the delivery economy which I found pretty good (and assigned as a reading for my class). https://podcasts.apple.com/us/podcast/delivery-wars/id1465767420?i=10005255… Some of the episodes/seasons of Command Line Heroes. https://www.redhat.com/en/command-line-heroes Last, but not the least, my own podcast (well, technically, these are my lectures when I taught my course The Social Life of Computing asynchronously in Spring 2021, but I tried to mimic the style of my favorite narrated history podcasts): https://soundcloud.com/user-118533348/sets/the-social-life-of-computing. There's a lot of social history of computing in there if they're of any use. https://soundcloud.com/user-118533348/sets/the-social-life-of-computing Hope this is useful! Best, Shreeharsh _______________ Shreeharsh Kelkar http://www.shreeharshkelkar.net

1 0