I remember being forced to learn this in university.

I started CS from the POV of someone with several commercial projects under the belt and at the time being fluent already in five or six different programming languages. But the university where I started had had an issue - they had been way to theoretical (imagine people writing their CS thesis on a mechanical typewriter, and professors telling us that one does not need computer access for mastering CS!). So they had been more or less forced to include at least a bit of real world stuff into their blackboard and paper world. Which resulted in a no-excuse-mandatory beginners course in Turbo Pascal in the first year and Turbo Prolog in the second.

And I was not alone. It was painful. They showed a programming task to be done on the overhead projector, and about 90% of us could have just typed down the answer without thinking and be done with the weekly assignment in five minutes. Nope. Instead, we had to follow (and join) a lengthy, boring, and worthless discussion about the very basics of programming, before we were allowed to work on it. And woe to us if we did not follow the precise path that we had been "taught" in that lesson, even if it was done in a way that no normal programmer would ever implement it.

If they had given us all the assignments for the semester in one go, we would probably had finished them in one afternoon, including documentation and time to spare.

At least with Turbo Prolog we learned something new. First and foremost that there are strong reasons that nobody uses Prolog for serious programming.