
Boundaries
This blog is about boundaries, and it is the second in a series of four in which I explain my way of working. It may seem playful or unorthodox, but there is a method behind it.
I come from an industry where people thrive on hot air.
People in the English-speaking countries use “hot air” to describe complex language. The French use “aire brûlé”, while Germans say “heiße Luft.” They all refer to language that is too complicated. My goal is to communicate in plain language. Ironically, that’s why I chose the name.
This blog is about boundaries, and it is the second in a series of four in which I explain my way of working. It may seem playful or unorthodox, but there is a method behind it.
Use cases description is difficult but essential. It describes the process and functional application of tools. In our world, these applications are often IT functions. It is by no means the intention to mix this functional approach with the technical realization. That is the conversation between the system designs and the architect/developer.
Sorry! I’m an older man and I’m not getting it anymore. In November 2021 I received an email from a Polish colleague. A woman in her thirties. She was annoyed
A historic observation about how humanity got to the point that they have computers and still store their content like 8000 years ago. There are alternatives.