We Need to Talk About Pseudocode

Pseudocode for Computer Science GCSE and A Level

Pseudocode for Computer Science GCSE and A Level is supposed to provide a way of describing algorithms which is simple, clear, unambiguous and language-agnostic.

However, we have a language which meets 3 of these criteria already – Python!!

As for the fourth, Python syntax is so clear that the intent of an algorithm written using it is generally obvious. And here’s the thing – it’s usually much clearer than the same algorithm expressed in exam-board pseudocode! In my view, the pseudocode required for all the Computer Science GCSE and A Level exam boards is a hindrance rather than a help to students learning to program and to write and understand algorithms.

Not to pick on any exam board particularly but seriously:

SEND ‘Have a good day.’ TO DISPLAY


print("Have a good day")




name = input() # str

What is the benefit?

Or how about this from CIE GCSE?

HighestMidday ← -999
FOR Count ← 1 TO 7
 IF MiddayTemperature [Count] > HighestMidday
  THEN HighestMidday ← MiddayTemperature[Count]
 MiddayMonthDay/MiddayWeekday ← Count
NEXT Count
PRINT 'The highest midday temperature was ',HighestMidday, ' on
day ', Count 

(Mark scheme indentation.)

Does it really meet the requirements for clarity and simplicity?

The use of “pseudocode” by Computer Science exam boards means that official teaching and assessment materials often contain serious errors, as pseudocode can’t ever be tested.

There is an historic reason for the horribleness of exam-board pseudocode: older languages like BASIC and Pascal. Many, if not all, of the exam boards use a form of pseudocode which dates back to the syntax of these languages.

It’s a bit like the argument about learning Latin vs learning Spanish, which is an immensely more useful language for most purposes, yet is much easier and has similar vocabulary, hence paving the way for those who wish to study Latin later on. Except for one thing – exam board pseudocode doesn’t have any use beyond the introductory level at which is is supposed to be used.

So why oh why do they insist on making students learn a more difficult and convoluted way to express algorithms than that offered by an incredibly popular and highly regarded existing language which they are already learning anyway???

An example of Useful Pseudocode

Now having said that, pseudocode CAN very useful. It just needs to be done at a level where is is actually worth doing, and in a syntax that is relevant to modern programming languages.

Take this example:

Pesudocode in Computer Science GCSE and A Level

from My Code School.

it is simple, clear and actually useful. You may not like the braces-style notation if you are unfamiliar with it, but it mimics the syntax of a multitude of important modern programming languages (Java, JavaScript, PHP, C++ etc..)

If there were a fully supported and recognised qualification for students that focused on actual programming/software development, then I believe the effective use of pseudocode could be valuably included.

So what to do? Well, I think exam boards should remove pseudocode from the Computer Science GCSE and A Level syllabuses.

While the exam boards insist on students learning pseudocode, I recommend the following approach: just get good at programming and then memorise the syntax for your particular exam board’s pseudocode and practice translating you code into that.

There are some great things about GCSE Computer Science and A Level Computer Science, but pseudocode is not one of them in my opinion.

Here’s a couple of pseudocode guides for reference:

Let me know in the comments how you feel about exam-board pseudocode for Computer Science GCSE and A Level.

Happy computing!

Sharing is caring!

1 Comment on “We Need to Talk About Pseudocode

Leave a Reply

Your email address will not be published. Required fields are marked *