Skip to main content

Scala Design Patterns Book Review

Introduction
There are many books about scala, some are both advanced and incomprehensible to most, some are not only simple and introductory, but there is currently only one book which managed to touch the sweet spot of a balance between presenting advanced topics and being comprehensible. This book is Scala Design Patterns by John Hunt.
Scala Design Patterns
I don't read it because of the design patterns!
I mean you can read this book in two ways. First way as a standard scala design patterns book. But the way I read it, is as a book written by an excellent writer who knows to explain himself, excellently, and as he want's to describe the design patterns in scala language, he describes scala concepts, and he manages to do it much better than every book i have seen so far!
What the book covers
So what does the book cover, or what did I learn from it? many things I found hard to grasp by other books! here is the list:
  1. Mixin composition - Will guide you on how to compose functionality
  2. Multiple inheritance and scala - Will show you how scala solves or get's around the multiple inheritance problem
  3. Linearization - The linearization process is the process by which scala get's around the multiple inheritance problem, here is a clear explanation of it!
  4. Testing traits - Best practices for testing traits the scala way
  5. Traits vs classes - When do you prefer classes to traits and vice versa how to properly combine them
  6. Implicits - Advanced usage of implicits - again clear and great explanations
  7. Algebric data types and class hierarchies - An excellent explanation of ADT
  8. Polymorphiosm and scala - The way scala views polymorophism pitfalls and how to utilize it
  9. Self types and when to use - What is a self type how to use, again excellent description with real world examples
  10. Stackable traits
  11. Typeclasses
  12. Lazy evaluation
  13. Partial functions
  14. Implicit injection
  15. Duck typing
  16. Memoization
  17. Monoids
  18. Monads
  19. Functors
  20. Lens
Do you see the book is just amazing, and he does an excellent job describing these topics not as other books!
Conclusion
Scala Design Patterns by John Hunt is my favorite book to learn scala and functional programmning in scala!

Comments

Post a comment

Popular posts from this blog

API Design Paper Summary and Review

API Design Paper Summary Introduction Is building API a solvable question, how far can we get into having good API’s and what is a good API at all? these are all very hard questions, usually you know the answers once you designed multiple APIs and got experience and then reviewed the decisions you have taken. Fortunately there are papers dealing with this problem exactly, for complex API’s used by a huge amount of people, the Qt API for example a very populate framework for desktop GUI building, and today we are going to go through a summary of that paper.

“The Little Manual of API Design” is a very nice paper written by Jasmin Blanchette has released a paper while working in trolltech, which is a Nokia company. I found it to be very clear and concise, and reassuring what we think of API design. It’s a difficult task that includes both artistic, social, programming and scientific skills. We are going to summarize this paper for you.

When you write an API you combine a set of symb…

Dev OnCall Patterns

IntroductionBeing On-Call is not easy. So does writing software. Being On-Call is not just a magic solution, anyone who has been On-Call can tell you that, it's a stressful, you could be woken up at the middle of the night, and be undress stress, there are way's to mitigate that. White having software developers as On-Calls has its benefits, in order to preserve the benefits you should take special measurements in order to mitigate the stress and lack of sleep missing work-life balance that comes along with it. Many software developers can tell you that even if they were not being contacted the thought of being available 24/7 had its toll on them. But on the contrary a software developer who is an On-Call's gains many insights into troubleshooting, responsibility and deeper understanding of the code that he and his peers wrote. Being an On-Call all has become a natural part of software development. Please note I do not call software development software engineering because …

Recursion Trees Primer

Recursion trees.

Controlling the fundamentals stands at the cornerstone of controlling a topic.  In our case in order to be a good developer its not enough or even not at all important to control the latest Java/JavaScript/big data technology but what's really important is the basics.  And the basics in computer science are maths, stats, algorithms and computer structure.

Steve wosniak the co-founder of apple said the same, what gave him his relative advantage was his deep understanding of programming and computer structure, this is what gave him the ability to create computer's which are less costly than the competitors (not that there were many) and by the way there were 3 founders to apple company one responsible for the technical side, one for the product and sales (Steve Jobs) and the third responsible for the company structure and growth, each of the three extremely important, it was not only the two Steve's but that's a topic for another episode.

And with that l…