It was not exactly what I expected (I expected a much deeper dive into functional programming), but I enjoyed it a lot overall.
What I liked the most: -It was not exactly what I expected (I expected a much deeper dive into functional programming), but I enjoyed it a lot overall.
What I liked the most: - It is very pedagogic, with lots of examples and repetition (in the line of the "Head First" series from O'Reilly, which I love). - Going through lots of great "good/best practices" in software development, beyond functional thinking. - I found especially interesting the last third of the book, with great examples of High-Order Functions, how to solve some async issues, coordinating timelines and reactive architecture. - Being somehow language-agnostic (the examples are in JavaScript, but extremely simple and vainilla, it could be any other popular language).
What could have been better: - Maybe too slow sometimes... - Missing talking about testing. - Missing more disclaimers about the dangers of some practices taken "to the extreme" (e.g. thinking about reusing before thinking about using, finishing with hundreds of tiny functions only used in one place and requiring lots of cognitive load to jump among them, etc.). - The author describes the "Onion Architecture", which is a well-known concept in a way which... well, sorry to say, but it is not the "Onion Architecture", he is reinventing it in a different way, which is misleading :-)
Overall: I would highly recommend it (unless your main goal is to go deeper into functional programming because you already have some experience) :-)...more
Loading...
