<@U0B8ZP13Q> I was in that same position back then...

# arrow

[raulraja]

@cedric I was in that same position back then when someone told me when I showed them some code that I was reimplementing map and foldLeft over an over when I needed to transform contents in collections.
I was used to Java (no lambdas) iteration with for loops and intermediate vars to capture state that I wanted back and while there was nothing wrong with it I learnt to express the pattern out of just doing it over an over. Felt disatisfied with an approach where I had to rewrite the same logic for different types over an over when the mechanics were the same and that is more or less how I got into FP.
I think mastering FP is hard but worth it in most areas. I would recommend beginners to learn the basic of the main funtions that are used such as map, fold, flatMap etc... with simple types like Option or List. These are functions that most of them already know how to use and then move on into digging deeper going into the FP type classes suchas Functor, Foldable, Monad etc. If you don;t code to abstractions directly and just concrete data types most of them already include the same functions and that is an easier first step. For example working with IO or Deferred.