Lesson Plan

• Describe how a compiler translates source code into machine code.
• Explain how an interpreter executes code line‑by‑line.
• Compare the advantages and disadvantages of compilers and interpreters across speed, development cycle, portability, error detection, and memory usage.
• Evaluate which execution model best fits different project scenarios.
• Apply this knowledge to recommend a suitable language/execution model for a given problem.

• Projector and screen
• Printed handout with comparison table
• Sample code snippets (C and Python)
• IDE access (e.g., VS Code, PyCharm)
• Interactive quiz platform (Kahoot or similar)
• Sticky notes for exit tickets

Begin with a quick poll: “Which programming languages have you used that require a compile step?” Follow with a brief reminder of how code is turned into something a computer understands. Explain that by the end of the lesson students will be able to identify the strengths and limits of both compilers and interpreters and justify their choice for a given task.

1. Do‑now (5'): Students list compiled vs. interpreted languages on sticky notes and share.
2. Mini‑lecture (10'): Define compiler and interpreter, show diagram of compilation vs. interpretation processes.
3. Guided analysis (12'): Examine the comparison table; discuss each aspect (speed, development cycle, portability, error detection, memory usage).
4. Group activity (15'): Teams are given a real‑world scenario and decide whether a compiled or interpreted approach is preferable, then present their reasoning.
5. Interactive quiz (8'): Kahoot quiz reinforcing key advantages/disadvantages.
6. Exit ticket (5'): Each student writes one advantage and one disadvantage of compilers and of interpreters on a sticky note.

Summarise the main trade‑offs discussed and highlight how the choice of execution model impacts performance and development speed. Collect exit tickets as a quick retrieval check. For homework, ask students to research a hybrid language (e.g., Java or C#) and write a short paragraph describing how it combines compilation and interpretation.