33-js-concepts VS Functional-Light-JS

Repository: leonardomso/33-js-concepts

2. 📜 33 JavaScript concepts every developer should know.

😎 A list of concepts that JS developers must know -> 33-js-concepts

+51.8k ⭐ ️=> https://github.com/leonardomso/33-js-concepts

Here’s a great resource doing exactly that : 33 concepts

So, I started learning about best practices from different schools of thought (Unix philosophy, SOLID principles, clean code), compilers, UI/UX design fundamentals, Svelte, advanced JavaScript concepts like the event loop, coercion, hoisting, closures, etc. Advanced React concepts like virtual DOM, reconciliation, advanced hooks, antipatterns, etc. among so many other cool things. My goal was to satisfy my curiosity about computer science in general while specializing in front-end development.

33 Concepts Every JavaScript Developer Should Know

Repository: getify/Functional-Light-JS

Functional-Light JS

And if you want to get to the "advanced" level of Javascript => https://github.com/getify/functional-light-js

I didn't really understand FP until I read Functional Light JavaScript by getify/Kyle Simpson. It is so well written and approachable by mere mortal coders. I'm not an FP wizard, but it is the coding paradigm I mostly use now. I've even adapted some aspects (e.g. composability) to the CSS I write using `var()`.

You can buy the book or read it on GitHub:

http://fljsbook.com/

https://github.com/getify/functional-light-js

Now he taught himself functional programming and GAVE ME HOMEWORK. I'm supposed to read this https://github.com/getify/Functional-Light-JS

Whenever I come across a cool concept in Computer Science, I try to think how to use it in real life scenarios. I've recently read Kyle Simpson's highly recommended book "Functional-Light JavaScript" that manages somehow to be thorough, innovative and fun to read at the same time. Near the end of the book Simpson discusses Monads, and demonstrates the concept with a cute example that is also a parable about the importance of humility and knowledge sharing. While I found this lesson valuable, I tried to come up with an example that could be useful in a real project.

They can, and they do quite nicely. A common approach is to be functional until it is no longer practical or efficient or fun, then wrap it in an imperative style. This is what Kyle Simpson imparts in Functional Light JS.