Skip to main content

Learning Scala online

As I mentioned on my last post I've been attending Functional Programming Principles in Scala course at Coursera. It's been three weeks now and I thought I should express my current feelings about the course.

Course arrangements


Arrangements on the course are just about what I expected. Series of video lectures per week, some quizzes in the videos and homework that's evaluated automatically in a matter of minutes. Homework assignments and videos are given on mondays and homework deadline is in about ten days from that.

On the first three weeks the lectures and homework has been about abstract presentations of entities and mathematical definitions.

Lectures


Lectures i.e. videos can be viewed online or downloaded and one can also download english subtitles for the videos and the slides shown on videos are also downloadable as pdf's. The subtitles could be helpful sometimes but the quality isn't that good, missing and wrong words, so I don't use them.

The lectures contains theory and basic examples of the weeks topics and mostly I've found them easy to follow.

Quizzes


The videos also contains quizzes in the middle or at the end of the lecture and the quizzes are also resolved in the videos. The quizzes objectives are usually explained so poorly that I don't even try to solve them myself.

Homework


The homework... these too are pretty poorly explained and the first thing to do before even trying solve them is to go to the courses forums and read through the assignment FAQ and some of the other posts where people like me don't quite understand what's the objective.

Once I've understood the objective some of the homework has been pretty straight forward but some of them go beyond my understanding and are way more complex than the lecture material presented.

The automatic evaluation process is nice except that sometimes the feedback doesn't help at all. 

Example: This week I got a feedback that filter (this is predefined method that I'm suppose to implement) is too slow and the execution was stopped at 40 seconds. Browsing through the forums I figured out that the problem isn't neccessarily on my filter but on my union (similar predefined method) and got some tips on how to improve my implementation of union. I managed to get my union faster and the evaluation error of my slow filter dissapeared. Too bad I had already lost 3/5 submissions trying to fix my filter.

Overall


So far I'm not liking this course. I hate that I'm working on some abstract entities and mathematical definitions. I'm a pragmatic person and I'm just hoping that the course gets more pragmatic or I'll lose my interest. I'm not loosing my interest on Scala just on this course. 

It seems to me that this course is about theory and abstract presentations of what ever more than it's about real life utilisation of functional programming and scala itself.

I'll try to keep myself motivated and hopefully in four or five weeks I can say that I did learn Scala during the course and I've forgotten the unpleasantry of the first three weeks.
Labels:

Popular posts from this blog

Simple code: Naming things

There are two hard things in programming and naming is one them. If you don't believe me ask Martin Fowler https://www.martinfowler.com/bliki/TwoHardThings.html . In this post I'll be covering some general conventions for naming things to improve readability and understandabilty of the code. There are lots of things that need a name in programming. Starting from higher abstractions to lower we need to name a project, API or library, we probably need to name the source code repository, when we get to the code we need to name our modules or packages, we give names to classes, objects, interfaces and in those we name our functions or methods and within those we name our variables. Overall a lot of things to name. TLDR; Basic rule There's a single basic convention to follow to achiveve better, more descriptive naming of things. Give it a meaningful name i.e. don't use shorthands like gen or single letter variables like a, x, z instead tell what it represents, what it does...
Read more

Simple code: Integration tests

Integration test is something that tests a functionality that is dependant on a external system e.g. a database, HTTP API or message queue. Integration vs unit tests The line is thin in my opinion. The integration part can be faked or a embedded services can be used in place of the actual integration point and with these solutions the interaction with the external system is bounded in the test context and the tests can be executed in isolation so they are very much like unit tests. The only difference with this type of integration test and unit test is that the startup time of the embedded or faked system usually takes some seconds and that adds total execution time of the tests. Even though the total test exection time is longer all the tests need to pass and all the cases need to be covered whether there's external systems involved or not so the importance is equal between the test types. This is why I wouldn't separate unit and integration tests from each other within the co...
Read more

Simple code: Simplicity

Simplest solutions are usually the best solutions. We as software developers work with hard problems and solve a lot of small problems every day. Solving a hard problem itself is a hard job. Though in my opinion it's not enough to solve a hard problem in any possible way but a hard problem should be solved with a simple solution. When a developer comes up with a simple solution to a hard problem then they can declare the problem solved. First a disclaimer. Coming up with a simple solution to a hard problems is itself a very hard problem and takes a lot of time, effort and practice. I've seen my share of "clever" solutions for hard problems and the problem with those is that usually the solution itself is so hard to understand that depending on the size of the problem it may take a developer from hours to days or even weeks to understand how that "clever" solution works. It's a rare occasion when a developer has come up with a simple solution to a hard pr...
Read more