The capstone project has done a fantastic job of drilling in some of the important fundamentals taught in the rest of the courses. It is definitely worth taking if you've done the rest of the courses.
Good course, some of the assignments could have been more explicit with expectations in cases where specific implementation details matter but the forums were helpful in that regard anyways.
por Роман В•
Milestones 1-3 was OK but milestone 4 require a much more efficient solution. And the only info grader gives you is the message about timeout. It would be better if requirements for milestones 1-3 were harder to fullfill or milestone 4 would not depend on previous code. But it depends and if your solution is inefficient it's very painful to search the problem all around the code. It's offered to use spark and other tools in this project but using spark is also painful. I get inconsistent result from grader with occasional OutOfMemory exceptions, but this project cries to be implemented with spark. I've learned something during this course but it was too stressfull and painful.
por Patrik I•
I'm sad to say that the last course in the specialization was the worst. The grader functions made it quite cumbersome to use Spark, which the test of the specialization was about.
You cannot use Spark throughout the course, because of the grader functions. You have to jump in and out of the Spark domain, which hurts performance and will not allow you to write a complete Spark program.
por Iurii S•
Would have liked more tests provided with the capstone to supplement often vague specifications. Feedback from autograder is often obscure as well as it refers to some input parameters of the randomized test - hard to take guidance in code improvement from it.
por David P•
Tough to design a capstone for a course, but I was never really able to get excited about the capstone project. It felt tedious. Not sure if this is the course organizers fault thought...
por Jędrzej B•
More about number crunching than fp. The dataset is within the jar, which caused a lot of problems and excluded efficient solutions (and the course is about efficiency as well).
por Kyle L•
I have finished previous 4 courses, they are excellent. But this one not easy to understand, doesn't have some simple test cases.
Lots of ambiguity in the course assignment, especially the 5th week one. Also response from teaching staff is very poor.
Overall I liked the course but some of the grading output was hard to understand what exactly I was getting wrong.
It was too algorithmically and math heavy. Also, it would have been good to have more videos.
por Canh S L•
Good project but instruction is a bit draft. Probably because I joined their first ever one.
por Ciprian L•
too much UI
por Will D•
I appreciate how hard it can be to write coding assignments. Especially in this case it seems as though the limitations stipulated by Coursera may have been quite restrictive for a big data spark project. However, I was really disappointed with this course. Rather than getting to test out my scala/spark skills I found myself trying to shoehorn functions into the methods provided by the grader only to have them fail unexpectedly with little feedback. Some more pointers on how to setup appropriate unit tests would also have been quite helpful. It seemed not so straight forward for spark.
por Nils-Helge G H•
There were too much ambiguity in the assignments. The structure and definition of the assignments made it unclear and difficult to solve with some of the included frameworks. It would be a lot better having a stricter definition and limit it to one or two frameworks that were suitable for the specific definition of the assignments.
por Adriaan T•
For a course that requires you to work on your own project, it still forces you to follow a code skeleton outline. This limits the freedom with which to tackle the project's issue. There is not much guidance or support from course organizers, which makes this course not very educative.