Chevron Left
Retour à Functional Programming in Scala Capstone

Avis et commentaires pour d'étudiants pour Functional Programming in Scala Capstone par École polytechnique fédérale de Lausanne

4.4
étoiles
488 évaluations
82 avis

À propos du cours

In the final capstone project you will apply the skills you learned by building a large data-intensive application using real-world data. You will implement a complete application processing several gigabytes of data. This application will show interactive visualizations of the evolution of temperatures over time all over the world. The development of such an application will involve: — transforming data provided by weather stations into meaningful information like, for instance, the average temperature of each point of the globe over the last ten years ; — then, making images from this information by using spatial and linear interpolation techniques ; — finally, implementing how the user interface will react to users’ actions....

Meilleurs avis

MP

Sep 08, 2019

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.

KB

Jun 14, 2017

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.

Filtrer par :

51 - 75 sur 80 Avis pour Functional Programming in Scala Capstone

par Fernando

Jun 06, 2018

Good Spark / Big Data project.

Provides a good example of real problem project focussed on Spark and big data analysis.

par Алексей Ш

Aug 03, 2017

The tasks are very interesting! Unfortunately, sometimes the causes for the failure of the tests are not clear.

par Natalija I

Jan 04, 2019

Capstone project is challenging specially because of the performance standards. I enjoyed solving the problems

par Andronik

Jun 16, 2017

Interesting project, but exercises were too simple. I was able to complete with course in 5 evenings.

par Carsten I

Oct 20, 2019

Tough but interesting, it definitely showed you the importance of writing unit test!

par Arthur

Apr 18, 2017

Good project enjoyed playing with the Scala.ja

par Wolfgang G

Sep 01, 2017

pretty tough, but informative!

par Michael L

Jan 11, 2020

I did the original courses back in 2016 and have used Scala consistently in various roles. I've done so many courses, I wanted to just finish this one and complete the specialization. I think I'm familiar with various Typelevel projects, SBT itself (I wrote a cucumber plugin for it) and have used Shapeless and Cats in anger. I'm familiar with ScalaCheck and have done a few O/S projects. This course ... perhaps I'm being unfair, but the project doesn't feel 'idiomatic Scala'. I think the course could use some of the Typelevle libraries as a starting point and lead devs into how to write functional Scala. In my experience - Scala is used a) for a functional programming language b) to drive Spark. Just as people will use Python for numpy/tensorflow (e.g. you can't compare Spire with numpy). The ML niche is lost, so I hope the content of these courses will still be useful for another 5 years.

par Ryan S

Jun 12, 2018

I enjoyed this course, but I believe there are some errors in the grading code related to interpolating colors. I raised an issue about it on the week 5 forum but never got a response. The project was interesting, but it would have been nice if there was a way that we could have been a bit more free in how we designed the interfaces. If you were trying to use something like a spark RDD it made it pretty cumbersome, having to always fit everything to an Iterable at the end. ALSO, I tried to add a library when I was doing this to add the shapeless library to this to add some interesting features which would have made the code a lot more general. I spent days getting it to work, only to realize you library dependencies are not actually imported when you submit, it only runs with the base ones that were pre-defined. A warning about that would have been nice.

par Fleur K

Nov 25, 2017

The first couple of assignments I found harder than the rest, and also the best bits. I found myself enthusiastically telling my colleagues about the data files and the spark code to join them. After that it got a bit too simple perhaps. And a little contrived. Some of the curried functions you had to fill in were way different from what I'd have written if I'd been staring at an empty screen and even after the course I've still not learned why I'd want to use this setup. The Signal bit in the last assignment was just plain silly, I think. It remains completely unclear why you'd want to use Signals here, other than that you want to refer to materials from the reactive programming course, and the sample code for the update doesn't actually work because the update method is protected.

par Васеев Р В

Jun 24, 2018

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.

par Iurii S

Nov 20, 2017

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.

par David P

Jun 16, 2017

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...

par Kyle L

Jul 22, 2017

I have finished previous 4 courses, they are excellent. But this one not easy to understand, doesn't have some simple test cases.

par Partha

Mar 20, 2018

Lots of ambiguity in the course assignment, especially the 5th week one. Also response from teaching staff is very poor.

par joshua

Jul 17, 2017

Overall I liked the course but some of the grading output was hard to understand what exactly I was getting wrong.

par Mikko L

Apr 30, 2017

The topic of capstone is great, but the milestones, and their APIs direct towards bad solutions.

par Anton K

May 25, 2017

It was too algorithmically and math heavy. Also, it would have been good to have more videos.

par Canh S L

Apr 21, 2017

Good project but instruction is a bit draft. Probably because I joined their first ever one.

par Joaquin D R

Sep 27, 2019

Milestone annoyingggggggggg

par Sergey G

Nov 12, 2018

Buggy grader

par Ciprian L

Jan 19, 2018

too much UI

par Will D

Jul 16, 2019

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.

par Nils-Helge G H

Jul 13, 2017

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.

par Adriaan T

Apr 12, 2017

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.