Skip to main content

Course completed

As I wrote in previous posts I've been attending a course Functional Programming Principles in Scala on coursera. I've completed the course and will write my final thoughts of the course this time.

First weeks


The first three weeks was like a  boot camp to drop out everyone who's not fully commited to the course. I've written about the first weeks in a previous post so I'm not going to repeat myself.

Weeks four and five


Weeks four and five were a positive surprise in two different ways. First of all the subjects were much more interesting and practical than in previous weeks. The second nice surprise was that the homework for the two weeks was combined.

Week four was about pattern matching which is a essential part of Scala and I found it to be a very interesting concept, easy to understand and it can simplify the code.

Week five was about lists. Nothing shocking during the week as lists are similar to lists in Java but in Scala lists do have some operations that come from the world of functional programming that Java doesn't have. This week also introduced a new concept called tuples which is something I'd love to have also in other programming languages.

The last two weeks


Week six was about collections other than lists including maps, ranges, sets and vectors. This week also introduced Scala's for queries which can be very different looking than in OOP. The collections are very similar to ones in Java so nothing new there but interesting new operations to transform between maps and other collections.

Week seven the last week introduced streams and lazy evaluation where in both the value is evaluated when it's needed. Lazy evaluation can be applied to any type of value or function so it's not evaluated until it's needed. Streams are similar to lists where the first element has a value and the rest of the elements aren't evaluated until needed.

Final thoughts


First weeks was a real pain like a boot camp to drop off the students who aren't motivated enough. The middle of the course consisted on familiar concepts from OOP and introduced some functional properties of them. The end of the course put all the learned concepts in use and introduced some functional concepts that are not found in OOP.

In the end I did learn some Scala but even more I learned about functional programming and what it means compared to OOP. This course gave me more than I could ever learn by reading from books or by practicing by myself.

Now that I've completed the course I'm taking a break from studying and after a few weeks of taking it easy I'll be trying out my new skill set with Scala to get some more practice. 
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: 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

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