Demo videos' audio hisses all the time. The lecturer describes the commit method as if it was just flushing. The code examples/templates are intern-level: just ugly code-style-wise (PEP8 weeps tears of disapointment whenever it glances at these), undocumented (the lecturer even removes some instructions from the code, because does not remember why it had to be put there xD, despite boasting about this code having been polished "for two weeks"), or full of poor logic, and I cannot understand how the lecturer can boast so much about calling a `close` method at the end of the entire script while there is no try-catch-finally block that could ensure that the resource would be closed properly on errors or signals. There are special seconds-long sleeps put around the code so that he can ctrl-C at the proper moment xDDD. He boasts about no needing to write proper try-excepts "until sth blows up", but ofc nothing will blow up if one ignores all errors with `continue`s and without any error/warning logging. And, on top of that, some quiz questions or answers are unclear, including one that tries to make you choose whether `String.split`or `split` is a proper Python function to split a string, while neither exist at this point of strictness (because it is `str.split`).

Dr Chuck is a great teacher. Unfortunately for Assignment 4 of this course, I felt that the question was poorly worded and that led to a lot of students having a hard time understanding what was required to complete the task

Nonetheless, all courses in this postgresql series and its learning benefits outweighs this small bump.

The last two modules, the curse turn in the wrong direction, i decline the curse.