Wrapping Up
In spite of the elegant, concise, and fluent nature of the functional style, some developers often write code that’s hard to understand. The result of that is counter to what the paradigm is intended for.
As a fellow developer, take the time to encourage your team to practice good coding habits. In this chapter we discussed multiple things we have to keep an eye on as a team to make sure the functional style code is both less error-prone and easier to understand, read, analyze, and maintain. Show your empathy to fellow developers and follow these idioms to get the most out of this amazing programming paradigm.
In the next chapter we wrap up with a discussion about making good use of the functional style and address some limitations. ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access