Functional Programming In C#: Refactoring Tip 

Thanks for watching! Glad you enjoyed it.

😂

Thanks for the detailed comments Robin 👍

I wrote a book that shares many of these kinds of tips. It's focused on Typescript, but the tips apply to C# too: leanpub.com/refactoringtypescript Otherwise, keep an eye out for great C# blogs by developers who are posting good tips. A couple that I like are: - andrewlock.net/ - www.stevejgordon.co.uk/

Thanks!

Thanks!

lol Sometimes functional techniques can simplify your code, sometimes OOP can 🤷‍♂️

No, currying and higher-order functions are two different things. Currying takes a method that has multiple parameters and replaces that one method with a chain of methods that can be composed together. It's easier to understand if you see it ;) I'll shoot to do some videos on this in the new year 👍

@@jameshickey84 yes please.

no, it's not, unfortunately

Yes 🤫

Hey Luis, I've been using Visual Studio Code in Ubuntu for these videos :)

Thanks!

One of the examples I gave actually was returning a result - as you mentioned. LogMs allows you to wrap an anonymous method and capture the results. One of the focuses of functional programming is, as you said, to minimize side-effects. That's because functions with side-effects are hard to test and therefore aren't predictable. But functional programming has other focuses/benefits beyond this. It allows new ways to build abstractions that either may not be available in other paradigms or are just way easier to do in FP -> composition (using currying for example), expressions over statements, higher-order functions (which allow you to scope/inject dependencies), etc. I've got a few videos on these topics if you're interested 👍 There may be cases when you need to use a higher-order function that returns void. For example, perhaps the "expensive operation" grabs some data from a database, does some intensive processing on them and then pushes them back to the database. Maybe it fetches data from an API and stores the processed results in a file? In those cases, the function may not be "academically pure" - but that's one of the things I want to avoid with these videos. Sometimes academic ideas aren't the most practical. We need to perform "side-effects" all the time in the real-world - saving to ANY IO stream would be technically considered a "side-effect" given the rigid academic definition of a "pure" function. At some point, you come to a crossroad where using FP (as an example) has some great principles that you can apply all the time (even to your OOP programming) but can sometimes go to an extreme where it becomes unpractical for most use-cases. Hopefully that helps! Let me know 👍