nodebestpractices VS Functional-Light-JS

ah, but there is one more reason to return await. have a read.

View on GitHub

Flat structure: check out the structure recommended by node best practices, and check out how Nest.js does the structure. The more layers you add, the more complex navigation with the flat structure becomes. With the component structure, it stays easy to use no matter how many components and layers you have.

I am looking for a resource like https://github.com/goldbergyoni/nodebestpractices. I know Sql but I want to learn best practices. Can you recommend me resources for this?

Also, while learning nodejs + express, have a read on the best practices here.

Assuming you have fundamentals in place this repo of best practices can help line things up and link you to areas where you need improvement. https://github.com/goldbergyoni/nodebestpractices

Please don't call node.js single-threaded as this is not true and is annoying. To take advantage of CPUs, this could help.

There is no one way to learn all these but here are some resources: 1. Gooking algorithms [https://edu.anarcho-copy.org/Algorithm/grokking-algorithms-illustrated-programmers-curious.pdf\] 2. Algorithms in all languages [https://the-algorithms.com/] 3. Node js best practices. [https://github.com/goldbergyoni/nodebestpractices] 4. Refactoring [https://refactoring.guru/] 5. Learn about Clean Code and Clean Architecture from uncle bob. https://www.youtube.com/watch?v=NeXQEJNWO5w&ab_channel=StreamAConStreamingConferences

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.

I came across two resources recently which have helped me think through pragmatic functional programming in JavaScript. The first is this talk by Richard Feldman that does a great job of explaining the why of functional programming. The second is this book by Kyle Simpson which proposes a flavor of functional programming that is practical in JavaScript. There are certain areas where my opinions differ from Kyle's, but this book introduces pragmatic functional programming from first principals. Also check out the Mostly Adequate Guide to Functional Programming.