When creating the first automobiles it was good engineering to equip the car with a clutch mechanism. Electric cars have made them redundant. Same happens in IT. Old solutions are rebuilt without questioning.
Microsoft! I dare you, I double, triple or quadruple dare you, but this is something that you cannot establish.
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.
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.
True greenfield development is like a air. You know it exists but you cannot see it. In system design there is always a legacy that needs to be taken into account. The greenfield approach however means that you always need to consider: what if we could do it again based on everything we know now
What determines the matter of detail? Some people get totaly bananas in a discussion about the definition or abstration of a process or activity. If you ask a lawyer for…