Week 2 — Social & Ethical Considerations

Background

This week you went inside the machine — logic gates, memory hierarchies, the Fetch-Decode-Execute cycle, controllers, and ports. These feel like purely technical topics, and in one sense they are. But hardware decisions don't stay inside the machine. They shape who can participate in computing, who bears the cost when things go wrong, and who gets left behind when the industry moves on.

The scenarios below connect directly to the hardware concepts you studied this week. Each one asks you to look at a real or realistic situation where a technical decision — about chip design, data storage, device compatibility, or hardware standards — had consequences that extended far beyond the engineering team that made it.

As you read, keep in mind that most of the decisions at the center of these scenarios were made by reasonable people, often with good intentions. That is part of what makes them worth discussing.

How to Use These Scenarios

Read each scenario carefully. For each one, consider writing down your thoughts on the following questions before your small group discussion. You don't need to address every question — use them to help you think:

1. Who are the stakeholders? Don't stop at the obvious. Think beyond who might be "at fault" to include those who were in a position to catch a problem and didn't, as well as those who were harmed by decisions they had no part in making.
2. Where were the decision points? At what moments in the scenario could a different choice have been made? Who had the power to make it?
3. Were poor decisions made in good faith? Were they the result of carelessness, cost-cutting, or reasonable judgment that turned out to be wrong? Does that distinction matter?
4. What could have been done differently? What might have been the reasoning — technical, financial, or organizational — for not making a better choice?
5. What connects this scenario to Week 2? What specific concepts from this week's material are at the heart of the problem?

After working through these questions, begin to form some opinions about what went wrong and, where it feels appropriate, who bears responsibility.

Scenarios

Scenario 1 — The Flaw That Was Also a Feature

This scenario is based on a real event. You can read more here: Spectre and Meltdown — official disclosure site from the research teams.

In January 2018, security researchers from Google Project Zero and several universities publicly disclosed two related hardware vulnerabilities affecting nearly every modern processor made in the previous two decades. They named them Spectre and Meltdown. The affected chips included processors from Intel, AMD, and ARM — the hardware running the vast majority of the world's computers, servers, and mobile devices.

The vulnerabilities were not the result of a coding mistake in the traditional sense. They arose from a deliberate performance optimization called speculative execution: a technique where the CPU guesses what instructions are likely coming next and begins executing them before it knows for certain they are needed. This makes processors dramatically faster. It had been standard practice in chip design for decades. The problem was that under certain conditions, speculative execution left traces of sensitive data — passwords, encryption keys, private memory contents — in places where malicious programs could read them.

Fixing the vulnerabilities required software patches to the operating system, not new hardware. But those patches came with a cost: depending on the workload, they slowed affected systems down by anywhere from a few percent to over 30%. Data centers and cloud providers faced significant performance losses. Users with older machines found their hardware noticeably slower after applying security updates. Some chose not to patch at all.

• The engineers who designed speculative execution were making a reasonable tradeoff that the entire industry adopted. Does that change how we think about responsibility for the vulnerability?
• Users who applied the security patches paid a performance penalty to fix a problem they didn't create. Is that fair? Who should bear the cost of the fix?
• Some users — particularly those with older or lower-end hardware — faced a harder choice: accept slower performance or remain vulnerable. How does this connect to equity in access to secure computing?
• This vulnerability existed in hardware shipping since the mid-1990s. It was discovered by researchers, not exploited in a known attack. Does the absence of a known victim change the ethical weight of the situation?

Scenario 2 — The Data That Didn't Disappear

A mid-sized school district, facing budget pressure, decides to donate its aging desktop computers to a local community center rather than paying for professional disposal. The IT coordinator, pressed for time, instructs staff to "wipe" the machines by deleting files and emptying the trash before they leave the building. Several machines are also simply reset to factory settings using the operating system's built-in reset tool.

What the IT coordinator does not account for is that deleting files and performing a basic factory reset does not securely erase data from a traditional magnetic hard drive. The operating system marks the space as available but does not overwrite the underlying data. With freely available recovery software, a moderately skilled user can retrieve deleted files — documents, photos, browsing history, cached passwords, and in some cases student records — from a "wiped" drive in a matter of minutes.

Several of the donated computers contain recoverable files including staff emails, a spreadsheet with student names and ID numbers, and cached login credentials for the district's student information system. No breach is reported. The community center staff who receive the computers are unaware of what remains on the drives.

• This week you learned about the difference between volatile and non-volatile memory. How does that distinction explain why "deleting" a file doesn't actually remove it from a magnetic hard drive?
• The IT coordinator acted quickly and with good intentions. Does intent affect responsibility when student data is involved?
• Who are all the stakeholders in this scenario? Think carefully — some of them may never know they were affected.
• What would a responsible hardware disposal policy look like for a school district? What are the tradeoffs between cost, time, and security?
• Does the answer change if the drives in question were solid-state (flash) rather than magnetic? Why or why not?

Scenario 3 — The Upgrade That Left the Room Behind

A school district receives a technology grant and uses it to purchase a new set of laptops for every teacher in the building. The machines are modern, well-reviewed, and genuinely better than what teachers had before. There is one problem: the new laptops have only USB-C ports. No USB-A. No HDMI. No headphone jack.

The district's existing infrastructure was not purchased with this in mind. Classroom projectors connect via HDMI. Document cameras use USB-A. The computer lab's printer uses USB-A. Many teachers have USB flash drives with years of accumulated materials on them. Students in lower-income households who bring their own earbuds to class have wired headphones with standard 3.5mm connectors.

Adapters exist for all of these situations, but they cost money — typically $10–$40 per adapter, per teacher, depending on the type. The grant did not include funds for adapters. Some teachers buy their own. Others simply stop using the peripherals that no longer connect. In several classrooms, the projector sits unused for weeks while a purchase order works its way through the district's approval process.

• The laptop manufacturer made a legitimate engineering decision to move to USB-C only. What were the likely justifications? What did they not account for?
• Who bears the actual cost of this transition in a well-funded district? In an under-resourced one? How does that difference matter?
• Is there an obligation on the part of hardware manufacturers to consider the downstream impact on institutional buyers like schools? Or is that the district's responsibility to anticipate?
• If you were advising a school district on a technology purchase, what questions would you add to your checklist after reading this scenario?

Scenario 4 — Your Port or Mine?

This scenario is based on real events. For background on the EU's decision to mandate USB-C, see: European Parliament — Common charger: EU negotiators agree on USB-C standard (2022).

For nearly a decade, Apple sold iPhones and iPads using a proprietary connector called Lightning — a port Apple designed, owned, and controlled. It was not compatible with the USB standards used by nearly every other device on the market. Consumers who owned both Apple and non-Apple devices needed separate cables for each. Accessories — speaker docks, car chargers, keyboards — built around Lightning only worked with Apple hardware. Schools that purchased Apple devices had to stock Apple-specific cables and charging equipment.

In 2016, Apple removed the standard 3.5mm headphone jack from the iPhone 7, citing engineering advantages: a thinner device, better water resistance, and a push toward wireless audio. Users who wanted to use wired headphones now needed a Lightning-to-3.5mm adapter — sold separately. Users who wanted to charge their phone and use wired headphones simultaneously needed a different adapter, or a third-party solution. The move was widely criticized. It was also widely imitated: other manufacturers followed within a few years.

In 2022, the European Union passed legislation requiring all smartphones sold in Europe to use USB-C as a common charging standard by 2024. Apple announced it would comply and began transitioning iPhones to USB-C starting with the iPhone 15 in 2023 — a transition it had resisted for years while the rest of the industry had already moved.

• Apple's proprietary port strategy was legal and, for a time, profitable. Does legality and profitability settle the ethical question?
• Who bore the real cost of Lightning's incompatibility with other standards? Think about individual consumers, schools, and lower-income families separately.
• The removal of the headphone jack was framed as progress. For whom was it progress? For whom was it a burden? Were those groups the same size?
• The EU ultimately forced a hardware standard through legislation. Is government regulation of physical port standards an appropriate use of regulatory power, or an overreach into product design? What values are in tension here?