A software always consists of data and behavior (business logic). The behavior are the (business) rules that define what the software should do – in a very easy form, think of a function like a + b = c. The function (beh
As a not-native english speaker, I sometimes bump into topics that conceptually are rather easy, but in fact much harder (for me) to grasp than they ought to be, because for a native english speaker they are probably sel
This weekend, I did some performance testing with ConcurrentLinkedQueue. Then, based on work requirements, I programmed a concurrent primitive array of fixed size, more or less like this: package com.marcusbiel.javacours
I am a Java developer since 2001. Over the years I came to realize that most teams / companies are totally ruled by fear. Fear to touch the code, fear to touch the production system, fear to touch the test system, fear t