The problem is not &quot;production code&quot;, but library code. I write a lot of business code in Scala, and a large majority of it is very easy to read for the newcomers we have. What is absolutely terrifying is what happens when you look under the covers: If you look at the implementations of libraries, as a newbie, you will want to run away, because you need to understand many language features before you can even understand a thing.<p>This is why I ended up writing a series of articles on practical implicates. Implicits are pretty much unavoidable, but the scale&#x27;s website documentation is appalling. But if they are explained through examples, and shows how, and when, it makes sense to use them, we can deal with them reasonably.