Yet again on the misbehaviors found in the Scala codebase I have inherited, and wrap up of the series.
#OurFathersFaults #Scala #SoftwareEngineering #AkkaAntipatterns
On the troubles related to concurrent programming in the actor model
On the problems encountered when trying to skip details and creating single state state machines.
On the trouble you face when you attempt to compose actor behavior by inheritance.
On the troubles you may incur when trying to conciliate the (untyped) actor model with the (typed) OOP world.
After the first four posts of “Our Fathers’ Faults” it’s time to turn a specific aspect of the application – the Akka framework. The code I’m managing is strongly based on this framework offering endless inspiration for misuse and abuse. Before going straight to the sins parade, I think it is proper a brief introduction
Continue reading: Our Fathers’ Faults – Akktors and Ekkstras
on the troubles coming from letting Scala infer the types of functions and expressions.
on the abuse of function composition from the software engineering point of view.
on the abuse of custom operator definition in Scala
on the misuse of Option[T] in Scala sources.