On the way home after the first post on this blog, I was thinking that in a short while there is a huge chance that the things I write here will get embarrassingly obsolete. There is also a huge chance that the words I write here have not the same weight as they do in my head.
There is a code debugging method in programming called Rubber Ducking. Let’s say the programmer is trying to find what is wrong with his code. He has written the code based in a certain logic, which makes perfect sense in his head, and “there is absolutely no reason why it would not work”. After various line-by-line scanning attempts, him and a rubber duck, will have a serious sit down, where the programmer will tell the duck what is trying to do and how he is trying to do it. In details.
The process of speaking to an inanimate object will give the programmer the chance to listen to himself and perceive the dissonance between his actions and beliefs. And find the bug.
I wish this blog will be my rubber duck on the conceptual technology thoughts that rise while in reverie.