Very challenging. Great course/project/specialization

Great course and specialization! Many thanks!

This entire Scala series has been excellent.

Great course, I learned a lot. Thank you!

Well structured. Interesting subject.

Thank you. The course is really nice.

Thanks for designing the course.

Very fun and enjoyable project!

Thank you! Learned a lot!

week 2,3 very hard......

It was very practical.

Scala is super duper!

Nice hands on Course

Great Hands on

Great course!

Excellent

The best

Thanks

I've read a lot of reviews before me and see that they mentioned several cons: off-topic programming assignment, imbalanced difficulty distribution and instable grader, vague feedback information.

For the few points mentioned above, I'd say I've experienced all of them indeed, it's true.

But for a project that's to be called "real", you're gonna have to adapt yourself to production environment and work like a true professional. That means you gotta tolerate faulty situations and ambiguous specifications. (Quite often, you don't know WTF they want, but you'll eventually come around and hand in a piece of code that runs smoothly with the right output.) It's something you deal with every day if you work in a tech firm as an SDE, RSDE, etc..

In terms of this kind of blank-filling programming assignments, it's just fine for me. Some argue that they should allow us to write everything from scratch and judge the grades by the output, allowing more flexibility for the developemt process. I think the skeleton code is simple enough, leaving enough freedom for you to mess around. If you allow me to start from scratch, I'm gonna finish it with C++ or Python.

The one thing I say they should really fix is the instability of the grader. Random failures and insufferable waitings are the two things that take away most of the fun. The programming assignment itself wasn't so hard, but was made unnecessarily much harder by these two factors.

For the sake of the previous four courses, I can spare 4 stars. But I understand those 1 stars.

I really enjoyed this course - it goes from the very basics of Spark and tests your ability regarding Scala knowledge.

The capstone project is really well structured, but at times it felt like the instructors could give more information concerning some definitions around the project, i.e. how all of the case classes from the models file interconnect or relate to each other. By the end of the project it would be helpful explaining how the Layer class was actually structured as well.

In reality my opinion of this course is 4.5 out of 5 - I think the instructors made an admirable job trying to convey most of specialization concepts into the capstone, so congratulations :-). If not for some of the aspects above, I would rate it 5/5.

A good project broken down into stages that can be independently tested to produce a final product that is both complex and interesting. The forum didn't have any of the TA's responding during my period and as such mean't that any concerns that I had were not being addressed. I had particular concerns with the grader input data where I had issues with its output. Apart from that a great way to put all the skills of the Scala Specialization into use.

Excellent capstone that lets you test your knowledge of Scala in a (semi)real project environment. Though i found that the main difficulty for me was in understanding the context of geographical computations. Making it difficult to find if not passing test was due to error in my code or in my understanding of geographical context.

Interesting project and fun to work on.

As with many of the other courses, could benefit from providing a few tests. Even after writing property-based tests using ScalaCheck there were some grader results that I was unable to reproduce.

In the end, still worth the time and effort invested.

The course is great, but if you pass all tests, in Week 4 you can get the certificate. The project is linked to Week 1, which is weird because doesn't match well with the schedule set in Coursera.

For a lot of sections one couldn't really use Spark, said sections were restricted to translating Spark datastructures to Scala collections and working with those.