Students should understand that most computer programs are written in…

The idea

High-level languages such as Python, Java and C# use readable words, familiar symbols and structured constructs, so a programmer can express an algorithm without tracking individual memory addresses or processor instructions. This makes programs quicker to write, easier to read and maintain, and far easier to debug, because a line such as a loop over a list states intent directly. High-level code is also portable: the same source can be translated for different processors by a compiler or interpreter, rather than being rewritten for each machine. Low-level code, by contrast, is tied closely to one instruction set and is harder for humans to follow. The trade-off is that high-level source must be translated before the processor can run it, and the translation can add overhead.

What earns the marks

• High-level languages use human-readable words, symbols and structured constructs, making programs easier to write and understand.
• Programs are easier to read, maintain and debug because the code expresses intent rather than machine-level detail.
• High-level source is portable across different processors, needing translation rather than a full rewrite for each machine.
• Translation by a compiler or interpreter is required before execution, which is the cost of using a high-level language.
• Low-level code is closely tied to a specific instruction set and is harder for humans to follow, so it is used less for general programs.

Common mistakes and how to put them right

• Assuming high-level programs run directly on the processor without translation.

  Put it right by stating that a compiler or interpreter is needed first.

• Claiming high-level languages are always faster to execute than low-level code.

  Put it right by separating ease of writing and portability from runtime speed.

• Confusing readability with machine efficiency.

  Put it right by explaining that readable constructs help the programmer, not the processor.

Exam tips

• Link each reason to a concrete benefit, such as easier debugging or portability, rather than listing adjectives.
• Contrast high-level with low-level explicitly so the reason for the choice is clear.
• Mention translation as the trade-off so your explanation is balanced.