Why Functional Programming
✍📝 Why Functional Programming?
👨💻 #Confidence :
Code that you cannot trust is code that you do not understand. The reverse is true also: code that you don't understand is code you can't trust. What do I mean by trust? I mean that you can verify, by reading and reasoning, not just executing, that you understand what a piece of code will do; you aren't just relying on what it should do.
🦜#Communication :
It's widely estimated that developers spend 70% of code maintenance time on reading to understand it. That is eye-opening. 70%. No wonder the global average for a programmer's lines of code written per day is about 10. We spend up to 7 hours of our day just reading the code to figure out where those 10 lines should go!
📙#Readability
Imperative describes the code most of us probably already write naturally; it's focused on precisely instructing the computer how to do something. Declarative code -- the kind we'll be learning to write, which adheres to FP principles -- is code that's more focused on describing the what outcome.
#Confidence
#Readability
#Communication
Special Thanks : https://github.com/getify/Functional-...
Sur cette page du site, vous pouvez voir la vidéo en ligne Why Functional Programming durée heure minute seconde en bonne qualité , qui a été Téléchargé par l'utilisateur Functional Programming 06 novembre 2021, Partagez le lien avec vos amis et connaissances, sur youtube cette vidéo a déjà été regardée 22 fois et il a aimé 0 téléspectateurs. Bon visionnage!
