3 Simple Ideas From Functional Programming To Improve Your Code 

That would indeed be amazing. Happy to help too if needed

In principle, that’s a good idea. Unfortunately, it’s really not suitable for RU-vid as the algorithm favors videos that stand on their own (even the 2 or 3 part miniseries I post from time to time do less well than my standalone videos). I am thinking of offering something like this as an online program though.

@@ArjanCodes I would love to buy a complete course.

@@ArjanCodes In the Python World, Using Django, it would be possible to build several stand alone apps that could be tied together. Though, that might still be too niche. Whatever you do or not, you are doing a great job. Thank you.

@@ArjanCodes yeah this would be a better option to have a complete course end to end.

Thanks so much Nathan, glad it was helpful!

Not just for python programming but software engineering as a whole. You can apply this principles to any language all you need do is learn with an open heart not a syntax or language oriented.

Thank you MrBachianas, will do!

Thanks Marty, happy you’re enjoying the content!

Thank you Golam, glad you liked the video!

Thanks Tommy, happy you’re enjoying the content!

Thanks so much, Caleb glad the content is helpful!

Thank you so much for sharing this! I'm glad that my videos are helpful :)

Good quote haha

Thanks Andrzej, happy you’re enjoying the content!

Thanks so much Chuck!

Glad you like the content and thanks for becoming a member!

Thank you so much!

Glad to hear! I'm always happy to be part of people's learning journeys.

Thank you - glad you find the videos useful!

You can use Ramda for JS or Lodash/FP. Those are very good to use with functional pattern with JS/TS. It's a bit more work using those libraries with TS though. But it's very doable.

Thanks so much, glad it was helpful!

Thanks so much, glad it was helpful!

Thank you Eduard, and great suggestion ;).

Thanks Chuks, happy you’re enjoying the content!

I think side effect also includes cases of mutating states outside of its inputs and outputs and local variables. For example, Python list append always returns None except exceptions. It is “deterministic”, but it is not side-effect-free.

I believe there's a cache decorator under the functools module

Thanks Anthony, happy you’re enjoying the content!

I don’t know if this is exactly the same, but I’ve found that partial functions is nice for having a single source of truth (or functionality in this case I guess). I’m my case it was in JS and went something like this: // NOTE: simplified for example (also copying into an IDE will make it easier to read) // most general form of fetching data function runFetch(baseUrl, endpoint, method, params, data) { // makes request to api using inputs } // Used specifically for user data function runUserFetch(endpoint, method, params, data) { return runFetch('userDataApi.com', endpoint , method, params, data) } // Specifically for GETting user data function getUser(endpoint, params) { return runUserFetch(endpoint, 'GET', params, {}) } // Specifically for GETting a users friends function getUserFriends(params) { return getUser('/friends', params) } // Specifically for POSTing user data function postUser(endpoint, params, data) { return runUserFetch(endpoint, 'POST', params, data) } // Specifically for POSTing a users login time function postUserLoginTime(endpoint, params) { return postUser(endpoint, params, { loginTime: Date.now() }) } As you can see with each new, more specific, function we make we reuse the more general form and set some input to a static value. This to me has one major upside, and that is EVERY time we fetch data we end up calling the same function (runFetch) and so now if we want to add something, (like maybe a cache or something), all we have to do is modify that single function to add that new feature. Or if we wanted to debug an issue with data fetching we only have to print out data in one place. TLDR: Starting with a general function, with lots of input options, we create more and more specific functions by calling the general form with some function specific input options. This allows us to have a single source of functionality so that if we ever want to modify that we only have to change one function. PS: This is just what Ive picked up along the way, not saying this is best practice or anything.

Thanks so much, glad you liked it!

Thank you Albert, will do!

Thank you! Cheers!

It is not our problem to solve. Languages should be optimised for these scenarios.

Thats pandas problem. In functional programming, these data structures were rewritten to be efficient, they just keep a copy of things that modified, not the whole structure.

@@karserasl object-oriented languages were initially designed for people who coded in C with all of its beatiful features. OO languages came, but the thinking remained imperative.

Pylance as you but has it on strict mode. He has a video about vs code extensions

Can confirm there's a strict mode. Use ctrl-, to open setting and search for "pylance strict" and it should pop up.

Good point, Simon!

I remember he said that he used the vim extension, but vim is fucking wild compared to most standardized editors (probably because the origins of vim is from before ctrl-c ctrl-v were a thing - in 1969 the Ed editor was created, which spawned Ex, which spawned vi, which spawned vim, which spawned Neovim and the vscode extension)

I like using ctrl + left/right arrow to jump over words, which I can combine with shift to make selections. End and Home are nice too.

@@NostraDavid2 I do that a lot. But I want to powerup even more my editing, if possible. If I notice that's not possible on conventional editors, I'll try different ones

Sure testability is most obvious: Maybe show a tiny unittest to make clear that its cumbersome to test for expected output.

that actually depends. in examples in this video, the argument names already contain information as suggested by the type alias. It might be better to just have the real type in the hint to provide the real signature

Thanks so much, glad you liked it!

Do you continue to do that with type hints?

@@raphaels2103 you mean do I stick with the practice? Yes. It's helpful to me.. so I keep doing it.

Thanks Priye, happy you’re enjoying the content!

I'm also interested to know about this "twin" 😂

Until what part were you able to follow the video? When did things start to get fuzzy? Please let me know as this is very useful feedback for me and I can incorporate that in future videos.

In the Star Trek mirror universe, I run a successful fashion channel but I write terrible code.

The shirt is good 👍🏻

Normally the knowledge is injected into my brain via a neural link, but unfortunately the data was corrupt, so I had to use another resource.

@@ArjanCodes 😆 🤣

Whats wrong with wikipedia?

I have experimented with using logging instead of print and it was confusing to the audience since extra boilerplate is needed to setup logging. I get that using printing as a logging solution is bad practice. But I’d argue that the way I use print is not logging: it’s what the example application actually does.

How about a video just on logging best practices? 👍😁

Thanks so much Yves, glad it was helpful!