Status Updates From Grokking Functional Program...

Done with chapter 8: IO as values.
It taught me how to think IO as values and separate side-effectful IO code from the rest of the application.
I would like to practice this in my future project, but I skipped some exercises from this chapter as they were mostly based on Scala 2 and depended on third party code, hence my laziness to get my hands dirty.

Done with Chapter 7: Requirements as types

In this chapter, we designed a problem with data types. Got to know some wonderful ADTs (Algebraic Data Types) like newtype, sum type with which interconnected requirements can be designed easily. Did Scala exercises on Option, Either, case class, enum, opaque type, case-match etc.

Done with chapter 6: Error Handling
Instead of throwing exceptions, FP lets you handle error like values. Function signature indicates if error is returned from it. Option and Either are two amazing concepts that are used to propagate errors, so you can write code without worrying you have to catch exceptions and do something.

Started part 2 of the book. Read the chapter "Sequential programs". Got officially introduced to flatMap and for comprehensions. Even though I used them before, after knowing the intentions to come up with these utilities, I have become a great fan of these two!

Grokked the last chapter of part 1: Functions as values. Key concepts
- Pass a function as parameter
- Return a function from another function
- Currying (the name comes from Haskell Curry)
- foldLeft
- Product type/case class to model data
I wish I could get these lessons before landing on my job. The examples are perfect for beginners, and also for me who jumped into production code w/o practicing these foundation.

Done with chapter 3: Immutable values
This chapter gives a tour of how we can mistakenly mutate values in a class. Then we are introduced to some Immutable libraries that let us code without worrying about mutation.

Done with chapter two: Pure Functions
Author takes time to explain the three characters of pure functions. With easy examples, over and over again we visit these three traits. Boy, now it's hard to write bad code.. he he.

Wow! What a good start! Giving me all the good vibes of a great book to learn a skill. In chapter one, it makes you fully comfortable about what you are going to learn, gives you the basics and makes you practice it. Excited about the next chapters!