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

Keychron Q1 vs GMMK Pro: A Comparative Review

Introduction Mechanical keyboards have become increasingly popular in recent years, and with a plethora of options available on the market, choosing the right keyboard can be a daunting task. In this blog post, I will be comparing two highly rated 75% mechanical keyboards - the Keychron Q1 and the GMMK Pro. Build Quality and Sound Profile The GMMK Pro has a stiff plate and does not move, making it suitable for mechanical switches that bottom out. This creates a noisy ring on the brass plate, especially with double-shot SA caps that produce a higher pitched metallic sound when bottoming out. The Q1, on the other hand, features a plate that sits on spongy spacers, which absorb the shock from typing, resulting in a smoother and softer typing experience. The plate also moves slightly when bottoming out, which is a unique feeling. When it comes to sound, both keyboards are not significantly different, but the GMMK Pro tends to be a little more hollow due to its stiffer plate. The K

Dev OnCall Patterns

Introduction Being 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 b

LeetCode 51 N Queens

The problem Input integer n Place n queens on n x n  board Q  means queen at cell .  Means empty space Queen can move in any direction Horizontally Up Down Diagonal neg + pos The Trick, let's say for 4x4 Understanding Notice that each and every queen has to be in a different row ! Notice that each and every queen has to be in a different column ! Notice that each and every queen has to be in a different positive diagonal ! Notice that each and every queen has to be in a different negative diagonal ! State - Set - is queen in column, posDiag (row-col), negDiag (row+col) Which rows have queen - do not have to store in state we just loop the rows Which columns have queen - store in state ! Which posDiag have queen - store in state! Which negDiag have queen - store in state! Trick posDiag -> row - column = constant Every time we increase row we increase column negDiag -> row + column = constant Every time we increase row we decrease column Loop 1st queen 1st row Can put first q