Content reasonably good. Some errors in quizes and assignments.

Assignments could use better descriptions and rubrics as often they did not test many of the features included in the assignment. Also one of the earlier assignments used knowledge that was not introduced until the following module.

Why say something in once concise sentence when you can say it in hundreds of words? There is so much unnecessary waffling in all these Go courses.

Almost all of the first 2 'weeks' is not relevant to Go. Moore's law indeed! Why?

The lecturer loves the sound of his own voice.

Contents are too basic. And I needed to wait so long time for a peer to evaluate my assignment. The worse, there is no guarantee when the evaluation will be done.

The instructions for the assignments are too vague. First two lectures in week 1 are not specific about go.

Sloppy, babbling presentation. Multiple inexcusable typos in slides, trying to learn a new programming language/syntax when the presentation contains syntax errors is just plain wrong. Presenter is disorganized, ramble and runs off topic. First week has NOTHING to do with GO. Programming concepts needed to complete second assignment given IN THE FOLLOWING week. I'm so grateful there isn't a fourth course in this series, I could not take much more of "professor" Harris. He might be fun to share a beer with, but not as an instructor.

I have loved the two previous Go courses, and been looking forward to getting to the course on concurrency. Unfortunately, this course embodies the very reasons I could not stand attending college. Right from the beginning, I had to sit through 39 minutes of lectures on a deep dive into topics that really are only relevant if I'm trying to specialize in hardware engineering. Now, I'm being asked to WRITE AN ESSAY covering those topics. I'm here to learn Go, not to dive into the hows and whats of modern CPU architecture.