Category: software
-
+
+
+
+
+
+
It’s been years since I was first warned how important a good data design is. As reminded recently by one senior engineer I know, data is very likely to outlive software. By a long time. From this perspective, data design may sound a bit scary. It might sound pretty demotivating.…
-
+
+
+
+
+
+
A software incident is defined as an unplanned interruption to an IT service or a reduction in the quality of an IT service. Any deviation from its normal or usual way of operation is an incident. The process to handle these incidents is called the incident management process. This is…
-
+
+
+
+
+
+
In words of an unnamed classic – life would be much easier, if we could have a look at the source code. Per this interesting calculation, there might be more lines of code written now, than stars in the Milky Way galaxy. Five times more. Possibly more. I do not…
-
I am now working with AWS services on a daily basis. I began to wonder what is this thing. WAF. As a software engineer I do have my concerns with architecture.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
-
In my previous article about principal engineers, I have laid out some basic thinking principles behind having more principal engineers. I have also stated and explained my disagreement to use the word architect in software engineering world. Today I would like to explore more into what principal engineers are. “Every…
-
+
+
+
+
+
+
One would not think that you would learn a bit on karate in IT. Although we do have kata’s in software engineering (the continuous practice to make us masters), as well as one of the most common materials for a kata, which is the karate chop (aka binary search).