Functions, Methods, and Interfaces in Go

This course is the only talks and powerpoint slides, there is absolutely no code, monitor screen sharing, etc.The courses talk about fundamentals and computer science stories. The entire specialization focus is less than 50% on the Go language itself. No Go mod, No libraries, No coding...For instance, The professor is about to explain a new thing and suddenly remember forgot to mention something before so he jumps to the missing point and then jumps back to continue. HARD to follow up...The quizzes have many typos/duplicates. That makes you fail!Overall strongly I do NOT suggest to waste your money or time on this specialization on Coursera.

Course is more theoretical than practical not worthy at all.

The course is extremely basic, not very complete, and full of errors that are being dragged through multiple months, the errors have been flagged on the forums, and they are never fixed. The grading is made by peer review - which could be a good thing, but the rubric for grading are could be completely automated, and it isn't.

For some reason, I'm not able to put rating to my current course, so I'll put it here:this course is not worth of 50 bucks a month - tl;dr - you are getting
misleading information, you won't get any support, you may dream about
course affiliates to be around to help you or others. You can do better googling
"what is golang about" and you'll get it faster and less expensive.The most insignificant thing at first - prof Harris talks about the GO lang which is fine, then he browses to some side facts which are not always true - well, it may lead to lower trust in this teacher. But - as I said - it's a small thing - you can still fact check every his statement.Bigger problem are the materials - slides are often showing code that is wrong (cannot be compiled even), assignments are full of misleading information or even it happens that the scoring cheatsheet is misleading - e.g. - give 5 pts if everything is OK, give 3 pts if "more than one" requirements were not met - so what should I do when I have exactly one problem facing?And the last - I would say the biggest problem - is this one. You are paying for this course, right? You are paying more than you are giving for some "all access" to all courses somewhere else. So you would expect some value for this. Well.... Wrong. This course (and its discussion threads, assignments, whatever) are not being reviewed by authors of this course, they are just not responding to you questions, notes, comments. It's the SAP (shut-up and pay) way. Instead of presence of some some responsible people - you are just left to your peers in the class (they may be none - regardless those fancy statements that you have to finish your assignment by "12/34 to be reviewed" - you'll be waiting weeks and weeks and paying and paying). Do you feel the difference? Instead having someone good that you could discuss your solution with, you may end up with someone that doesn't have a clue what he/her is doing and you depend on his/her decisions - if you are lucky enough and there's at least someone doing the same course as you.So - you are paying not a little amount for slides, that can be found anywhere on the internet, for videos with a person, his statements could be anytime easily disputed and for putting 0+ people together, you are a fool.

Too many errors in the content

some homework questions are wrong

There are obvious errors like ">" instead of "

Peer-reviewed assignments are problematic and frustrating. I would never pay for a course that didn't have a TF/TA or Professor grading the assignments. Students can't possibly make judgement calls on code; else the code becomes very narrow and cookie-cutter.

quite a lot of mistakes in study materials and tests

An ok course. Lots of annoying typos in the slides, and the instructor seems to stumble over some of the explanation. In the end, it did teach me the basics of go functions and OO concepts.

Negatives:Not an intermediate course, more like a beginner course for me. Too much background info which is not go related eg why functions, what are good properties of functions, this is too generic and beginner materialExamples are not good: bad variable and function names, non-practical or even confusing/misleadingPositives:Important topics are covered, explainations are ok (but could be better)

There were a few inaccuracies which might be confusing for newcomers to the language. It would be good if the instructor or someone else with editing permissions could take a look at the feedback and act on it.