Our Father’s Faults – Wrapping it up Posted on: 2020-01-23 by max Yet again on the misbehaviors found in the Scala codebase I have inherited, and wrap up of the series. #OurFathersFaults #Scala #SoftwareEngineering #AkkaAntipatterns
Out Fathers’ Faults – Actors and Concurrency Posted on: 2020-01-16 by max On the troubles related to concurrent programming in the actor model
Our Fathers’ Faults – Actors – Explicit State Posted on: 2020-01-09 by max On the problems encountered when trying to skip details and creating single state state machines.
Our Fathers’ Faults – Mixing Actors and OOP 2 – Acting is not an inherited trait Posted on: 2019-12-29 by max On the trouble you face when you attempt to compose actor behavior by inheritance.
Our Fathers’ Faults – Mixing Actors and OOP 1, Actors with methods Posted on: 2019-12-19 by max On the troubles you may incur when trying to conciliate the (untyped) actor model with the (typed) OOP world.
Our Fathers’ Faults – Akktors and Ekkstras Posted on: 2019-12-13 by max 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 introductionContinue reading: Our Fathers’ Faults – Akktors and Ekkstras→
Our Fathers’ Faults – Scantly Typed Language Posted on: 2019-12-05 by max on the troubles coming from letting Scala infer the types of functions and expressions.
Our Fathers’ Faults – The Chain of Death Posted on: 2019-11-28 by max on the abuse of function composition from the software engineering point of view.
Our Fathers’ Faults – Operator @!# Posted on: 2019-11-21 by max on the abuse of custom operator definition in Scala
Our Fathers’ Faults – Failure is not an Option Posted on: 2019-11-14 by max on the misuse of Option[T] in Scala sources.
