1 star lost because week 1 is unnecessary. Cool course, as it is easy to do in a week.

There are some errors on tests that have been flagged and haven't been fixed.

Much better when video is chopped up. Easier for microlearning sessions :)

I guess a final project should be their to develop then it would be great

I hope there will be a TA in future. The class is great enough.

Perfect course, with mix of theory and practical examples.

Practical session should be encouraged more

less explain on coding parts

It's really a good course.

Lack of visualizations

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.

The course is good but lacks more caring. The Coursera team that assembled the course forget to cut the videos and give proper labeling to the modules. So we have those bizarre names such as M123_4 , which are meaningfulness, and do not add any values to the course. The forums are "western land" with just "review my assignment that I review yours" requests, which is against Coursera conduct code including, and nobody is moderating those. Also, Prof. Harris could have used much more code. Concurrency is not an easy topic, and you'll have to search for a lot of content outside the course to complete the last assignment. That's a pity, because the specialization is very good and could have ended very well.

My critic is only about the content selection, Prof. Harris is great.

I miss more further concret thread concepts and assignments of go lang, like pools, more channel communication stuff and not so much technically informations about physical computer stuff in detail. Week 1 of this course was to much time on this pure technically topics without "hands on code". If these technically topics more a compact meaty advanced summary accross 10 minutes, i mean, would be better.

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

So, as someone taking this course, I already get WHY learning about concurrency is important. But what I really signed up for was to figure out HOW to actually work with it, especially since you said this course is aimed at programmers. So, gotta be honest, the first two weeks felt like a bit of a waste of time for me. I mean, those two hours could've been spent way better. In my opinion, those first two weeks should've been optional videos for folks who aren't familiar with the basics already, 'cause they didn't really connect much with the main stuff we're here to learn

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.