The course is well structured although it is a bit short. I was expecting to dig deeper into more asynchronous models. A better explanation of Actors would have helped. Also I felt that the exercises were missing the point of the lectures.

The lectures by Erik Meijer felt out of place and poorly connected to the previous content. Similarly, his lectures were tedious to follow. I would have preferred more on-scree time of the slides instead of the shared screen.

As a continuation from the previous course, "Function Programming Principles in Scala", I found this less focused -- especially with respect to the title. For instance, at times there did not seem to be a strong match between the programming assignment and the lecture material. Regardless, I still learned quite a bit and Dr. Martin Oderksy is an excellent video presenter. I am still surprised by how powerful Scala can be in a terse yet readable manner.

The course was really unstructured. The assignments were too easy and did not cover the material from the course. Several times there were further classes on a certain topic promised, which this course does not include. Week 4 was especially confusing. Concepts were used, which weren't introduced before. The end seemed rather abrupt. Overall the content from this course is really small compared to the previous course of the Scala Specialization.

This course was significantly less instructive than the first. Assignments did not lead me as constructively through the material. Also the few videos with the other lecturer in week 4 are very confusing, hard to understand, or even appreciate in light of all the other material. I do not think that I have understood futures and am glad it was not required for the last assignment as the answers aren't present in the material.

The lectures were not very illuminating and did not tie in closely with the programming assignments. There was very little focus on design. This course did nothing to answer the questions of why, if you were building a real-world software product, you should use Scala in particular or functional programming in general. It merely served to provide a few more examples of FP patterns without demonstrating their value.

Interesting course. Not sure it really covers functional programming design, it feels more of a brief introduction. The material is clearly a cut & paste from a different (and I guess longer) course. There were references to non-existing weeks, and to subjects that were not part of this course. That felt a bit cheap, considering that courses are not really free anymore. Positive experience, but not exceptional.

The topic very interesting as well as course assignments. But not so good as progfun1. It looks like some topics were thrown away. E.g. quick check assignment is not in a right place. Assignment about Streams is too complicated and does not illustrate streams well. There is not enough information about design - e.g. more patterns and guidance when to use mutable state with oop princilpes and when to use fp.

Too fast and dense material is being presented with little practice. For example. lecture on Monad describes what they are but doesn't use them enough in exercises. While i was struggling to grasp topic while viewing the videos and had to view them repeatedly. Exercises were very simple. So I am not sure what they are evaluating. I realise that building an exercise to evaluate this topic is harder too.

Decent follow up to the excellent first course. There are three programming assignments, all quite challenging and interesting. The second assignment followed a series of lectures on mutable states. However the assignment was all about Scalacheck which was not at all covered in the lectures. Strange. If you're unfamiliar with reactive programming (as I was) the material will be challenging.

This course introduces many important concepts in functional programming such as monads and lazy evaluation. Also you can find quick intodution to reactive programming in this course, however I want to know more about reactive programming. Week 4 is bad structed, it looks as if it was cutted from another course and pasted in this one. And I want more assignments to play with monads.

The lectures were quite interesting, especially the first two weeks and the ones by Erik Meijer. But overall course seems to be too blatantly put from several other courses which might be interesting to listen separately (e.g. FRP) and the assignment don't seem to cover the material from the lectures too well. Some very interesting concepts seem to be left out of the scope (actors)

While I hold the first course in high regards, this one is often incomprehensible, the new tutor is a lot worse than Martin was, and the topics are also a lot less interesting. Property testing was a new concept to me, I really enjoyed using it, and since I've incorporated it into my own workflow, but events, signals, coming from a javascript background, were just an annoyance.

Fantastic topic on itself, yet delivered in a rushed manner. Programming assignments are of uneven difficulty. The second assignment is all about a testing framework usage, not really aimed towards Functional Design at all. Feels like the material worth 10 weeks was crammed into 4 weeks.

You can still learn some important conceptions, so it is not a total waste of your time.

This course has some really good material but the way it has been presented is very disjointed and does not really do the job of properly illustrating Functional Program Design. Although topics such as Signal and FRP are interesting they serve little value in day to day use and assignments focusing on Futures would be far more beneficial.

Contrasted with the first course, this one isn't nearly as good. The videos were choppy and broken up into strange segments. The assignment had some extremely confusing instructions and I wasted tons of time reading the forum to try and resolve basic things. Don't get me wrong. I did learn some stuff but the overall quality was lacking.

Many of the lectures use concepts that were not introduced before, which is very confusing. On the third week, the lectures are completely disconnected from the assignments. The lectures from the last week feel out of order, but at least the assignment was able to connect everything.

The best thing from this course are the assignments.

The course in general is not as good as Martin Odersky's first course, but it still has interesting bits to learn about functional programming.

Everything topic feels very disconnected to each other.

Lastly, the last part of the course is specially disorganized. I didn't feel like the assignment captured everthing that was taught.

Material in the first few weeks was taught well and went together with the first course in the track.

The latter part of the course was not taught in such great depth and was not examined in the exercises either.

Consider making the first course longer and dedicating the whole of this course to the material in the latter half.

I was expecting this course to be more challenging than Functional Programming Principles in Scala but found this one easier in the end. The assignments were ok but I felt like they could have been more challenging and also that they should have tested my understanding of the course contents more thoroughly.

I have the sensation that this second part is not so well explained as the first one.

Week 3 was confusing. The assignment is not related to the video contents.

Week 4 was confusing too. The mix between Martin and the other guy's videos is weird. Also I expected much more reactive stuff.

A daily demanding course, which could have benefitted from more time spent in some areas - particular signals. The video explaining a sample Signal implementation was very rushed and provided too little detail on a lot of information that seems to be taken for granted.

Very hard to follow due to unsequenced lessons. Had a tough time with the exercise QuickCheck because I was not solving the problem. I have devising test cases to verify the solution. Rest of the content was good, but reactive lesson was quite short to start with.

At times, this course looks a patch work of videos without a clear continuity. It is a pity that one week has no assessment at all and the last week mostly on "Futures" does not assess them. Also it would have been nice to have a snapshot on Actors

The course needs a reboot. Some parts were merged with other and the whole thing lacks continuity. A few examples were poorly chosen. For instance, signals / reactive concepts would be easier to understand in user interfaces or graphics / games.

week 4 course "timely effects" with Erik Meijer videos are very hard o watch, the background and the slides are very distracting. Did not learn much with those videos, I had to resort to other sources to learn about lazy evaluation and futures.