When modelling information, it is important to balance easy to understand high level overviews with accurate and detailed models. In the beginning of a project, all there is are high-level overviews. Often they are not yet complete, and they are not very useful once you get into the details.
In this blog post I want to highlight a very simple yet powerful integration pattern: the notification pattern. The reason why it's not often used is because it does not map requirements one-to-one (and let’s be honest, it's also more complex than a simple point-to-point connection).
Since the introduction of the General Data Protection Regulation (GDPR) on May 25th, 2016 a lot has been written about privacy and protection. I would like to contribute with an addition on a topic that I value greatly, namely implementing Privacy by Design in our organization.
In December last year we heard a lot about the new zoning measure nicknamed “betonstop”. The objective is to allow no additional constructions by 2040. Construction works at Flemish level currently cover about 6 hectares per day. By 2025 this should be reduced to 3 hectares per day.
In december vorig jaar hoorden we allemaal over de 'betonstop'. Doelstelling is om tegen 2040 geen bijkomend ruimtebeslag te hebben. Momenteel is het ruimtebeslag op Vlaams niveau nog gemiddeld 6 hectare per dag. Tegen 2025 moet dit gereduceerd zijn tot 3 hectare per dag.
In my day-to-day business, I get in touch with a lot of people, and very often I realize that we're only talking about 3 main things: complex processes, inefficient paperwork and zero connection with colleagues. But in fact we're just talking about the all-known, almost sacred nowadays, "digital workplace". This game-changing combination of those two buzzwords is all around these days.