Sign In Request Beta Access
← Back to Computer Science

GCSE Computer Science 02 — Problem Solving & Programming

Public

Topics include Variables, constants and data types, Selection (if/elif/else) and Boolean conditions, Iteration: count-controlled and condition-controlled loops, Arrays/lists and string processing, Validation, authentication, and defensive input handling, Tracing and debugging (dry runs, breakpoints, logic errors), Testing: normal/boundary/invalid and expected outputs, and Searching and sorting in programs (choosing a method).

ComputerScience EN
216 cards
Study this deck on Deckloop

Preview Cards

A sample of cards from this deck.

Example explainer

A sample of the AI explainer you can generate for cards in this deck.

Translators and program execution (compiler, interpreter, assembler)

Translators convert code into machine code so it can run; different translators fit different workflows.

Key points

  • A compiler translates the whole program before execution (often producing an executable).
  • An interpreter translates and runs line-by-line (useful for quick testing).
  • An assembler translates assembly language into machine code.
  • Syntax errors are usually caught by the translator; runtime errors happen while running.

Worked example

Question

Why might a student use an interpreted language during development, even if a compiled language can run faster?

Solution

Interpreted environments often give rapid feedback (run small snippets quickly, easier debugging), which speeds up development and learning. Performance can be optimised later if needed.

Common pitfalls

  • Thinking interpreters 'convert to machine code once' like compilers.
  • Confusing assembly language with machine code.

Prerequisites

  • Hardware basics (CPU executes machine code)
  • Idea of source code
Further resources