Computer Science · 12th Grade

Active learning ideas

Automation, AI, and the Future of Work

This topic asks students to consider how legal choices shape technology’s future. Active learning works because students must compare abstract licenses, debate real stakes, and analyze visible artifacts. These tasks turn abstract rights into concrete decisions that mirror how professionals actually navigate IP and open source every day.

• Common Core State Standards
• CSTA: 3B-IC-26
• CSTA: 3B-IC-27

• 40–45 min
• Pairs → Whole Class
• 3 activities

Activity 01

• Inquiry Circle
• 40 min · Small Groups

Inquiry Circle: The License Match-Up

Provide groups with several software projects and a list of licenses. Students must determine which license is best for each project based on the creator's goals (e.g., 'I want everyone to use it, but they must share their changes' vs. 'I want to sell this and keep the code secret').

What new career paths are created when traditional jobs are automated?

Facilitation Tip

In The License Match-Up, assign mixed teams so that students who already recognize MIT or GPL can coach peers who know only trademarks or patents.

What to look for

Pose the question: 'Should governments implement a tax on robots or AI to fund social safety nets for displaced workers?' Facilitate a debate where students must present arguments for and against, citing specific industries or job roles that would be most affected.

• Analyze
• Evaluate
• Create
• Self-Management
• Self-Awareness

Activity 02

• Formal Debate
• 45 min · Whole Class

Formal Debate: The Ethics of 'Copy-Paste'

Students debate a scenario where a developer uses a small piece of open-source code in a billion-dollar commercial product without proper attribution. They must argue the case from the perspective of the original creator and the company's legal team.

Should there be a tax on robots to fund social safety nets for displaced workers?

Facilitation Tip

When running The Ethics of 'Copy-Paste', give each side a 3-minute lightning speech, then flip roles to press for counterarguments.

What to look for

Provide students with a short article or case study about a specific industry undergoing automation (e.g., manufacturing, retail, healthcare). Ask them to identify two jobs likely to be automated and two new jobs that might be created, explaining their reasoning.

• Analyze
• Evaluate
• Create
• Self-Management
• Decision-Making

Activity 03

• Gallery Walk
• 45 min · Individual

Gallery Walk: Open Source Success Stories

Students research a major open-source project (like Linux, Android, or Wikipedia) and create a poster showing how it was built and who owns it. Peers walk through the gallery to identify how these projects compete with proprietary giants like Microsoft or Apple.

Explain how the shift toward automation changes the skills required for the next generation workforce.

Facilitation Tip

During the Gallery Walk, station a large sheet for each success story so students can post sticky notes with specific evidence they found compelling.

What to look for

Students research a specific industry and its susceptibility to automation. They then create a brief presentation outlining their findings. After presentations, peers use a simple rubric to assess the clarity of the analysis and the evidence presented for automation risk and new job potential.

• Understand
• Apply
• Analyze
• Create
• Relationship Skills
• Social Awareness

A few notes on teaching this unit

Teachers should model skepticism toward the word ‘free’ by showing Red Hat’s annual reports and contrasting them with a proprietary vendor’s price list. Avoid overloading students with all license clauses at once; instead, let them discover the key differences through structured comparison. Research shows that when students debate real cases—like a student project accidentally violating GPL—they remember the clause far longer than if they merely read it.

By the end, students should clearly distinguish proprietary from open-source licenses, justify their own ethical stance on reuse, and cite evidence from case studies. Success looks like reasoned arguments, correctly matched licenses, and accurate descriptions of how open-source projects sustain themselves financially.

---

Watch Out for These Misconceptions

• During The License Match-Up, watch for students who assume all open-source licenses are the same.

  Direct teams to examine the actual text of MIT, GPL, and Creative Commons licenses in the handout, then circle the clauses that require source code release or allow proprietary reuse.

• During The Ethics of 'Copy-Paste', watch for students who claim unlicensed code is automatically public domain.

  Pause the debate and have students open GitHub repositories to locate the LICENSE or COPYRIGHT file in a repo they selected; ask them to read aloud the section that states what permissions the author grants.

---

Methods used in this brief

• Inquiry Circle
• Formal Debate
• Gallery Walk