The reason and the quest for having a for comprehension in C++
After six years of writing firmware in C++, I nearly forgot what it is like to develop in plain C. In fact, I remember I wrote quite convoluted C macros to implement template-like containers, therefore when I was handed a prototype firmware to contribute, I thought I was quite fine. After all, I needed just
Continue reading: From C to C++ and back, but not for the reason you may think
The worst form of inequality is to try to make unequal things equal – at least according to Aristotle. On the other hand, software engineering tries quite hard to deal with unequal things in the same way. Think for example to the file system concept, it is very handy to deal with data in your
Continue reading: C Strings, a C++ View
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.