The course material was very good, and the presenter did an excellent job. I was especially impressed that he gave background conceptual understanding, not just language syntax elements. Slides were pretty good, sometimes very good. But the web site was a mess! At the end, I waited four days (impatiently) for a dining philosophers project to be available for me to grade, so I could finish the course. It never showed up. Finally I went to the forums and responded to someone's request that I review his assignment, and that allowed me to complete the course. There was nothing, nothing in the course anywhere, to tell me that this was either possible or necessary. Why did the web site not give me an assignment to grade when there were multiple students begging to have their assignments graded in the forums? And do course assistants ever respond to forum posts? Very, very bad technical execution of the course.

Content was rushed very quickly. First week content was bit stretched. Although the content was relevant but stretched. Rather reading from slides, content could have being more interactive.

Good course. I think that is good for beginners or someone who has no experience with Go and programming in general. For more advanced, is quite too low in content

The class goes in sufficient details through the go concurrency features but more concrete examples would be useful to retain the material.

Too much details on concurrency basics, not suited for the ones with other programming language experience.

Shabby and messy

Light on content, with an emphasis on the very basics of concurrency and Moore's law. I was hoping that an intermediate course would jump right into the Go concurrency concepts instead of spending half the course on remedial concurrency topics.

It may be that the course isn't very fully attended in June of 2021, but I was having a hard time getting folks to review my assignments and/or finding assignments to review (you must review at least one for yours to be graded).

The concepts in this course are critical for any Go developer to know. However the course itself contains all sorts of extraneous information and could easily be done in two modules instead of four. There are many more go topics that could be included in this class instead of wasting time talking about Moore's Law and repeating information.

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.