Hello! Pretty neat content, I've been watching over the past couple days. Keep it up :D One thing, the account's profile picture reminds me of the logos used in the cats ecosystem in Scala. Is it safe to assume we can expect FP Scala content at some point? 👀
also, anecdotally, instead of 5 lines of plain simple for loop code you get 25 - with some additional functions/classes, or, you can conveniently replace a part of it with an external library...
You lose like 99% of the people when you start the part of over-abstracting "either", "left" and "right"... The "tuple" concept (and especially implementation) in many, many languages is harmful, the code you write (and then read, either by yourself, or by somebody else) turns into a steaming pile of turd spaghetti - "on which level, exactly, am I located right now? was it in the "key"/"left"/"value0" or ""value"/"right"/"value1" right there, two levels up?" In the real world, with real programming language (or at least if you don't want to have a total mental breakdown in a few months), you either create a dedicated class with an explicit name like, e.g. "ResponseAboutXWrapper" with the explicit methods like "boolean isSuccessfulResponse()", "String successfulResponseMessage()", "String errorResponseMessage" and so on, or at the very least create a "record" instead of a class, with similar explicit clear and understandable naming...
![[Advanced] On error handling in Functional Programming](http://i.ytimg.com/vi/O3V_lc3oifs/mqdefault.jpg)
![[Advanced] On error handling in Functional Programming](/img/tr.png)
Hello! Pretty neat content, I've been watching over the past couple days. Keep it up :D
One thing, the account's profile picture reminds me of the logos used in the cats ecosystem in Scala. Is it safe to assume we can expect FP Scala content at some point? 👀
Thank you. Yes 😉 My thoughts and ideas are all over the place. For now, I'm trying to cover FP concepts using a variety of languages
also, anecdotally, instead of 5 lines of plain simple for loop code you get 25 - with some additional functions/classes, or, you can conveniently replace a part of it with an external library...
You lose like 99% of the people when you start the part of over-abstracting "either", "left" and "right"... The "tuple" concept (and especially implementation) in many, many languages is harmful, the code you write (and then read, either by yourself, or by somebody else) turns into a steaming pile of turd spaghetti - "on which level, exactly, am I located right now? was it in the "key"/"left"/"value0" or ""value"/"right"/"value1" right there, two levels up?" In the real world, with real programming language (or at least if you don't want to have a total mental breakdown in a few months), you either create a dedicated class with an explicit name like, e.g. "ResponseAboutXWrapper" with the explicit methods like "boolean isSuccessfulResponse()", "String successfulResponseMessage()", "String errorResponseMessage" and so on, or at the very least create a "record" instead of a class, with similar explicit clear and understandable naming...