Skip to main content

Posts

Showing posts from April, 2026

Movie - The Instigators (2024)

 

When Personal Life and Professional Life Intersect

Based on a LinkedIn post originally published on 9 February 2026 One of the best periods of my professional life was the time I spent working for Compaq and Hewlett-Packard. I was exactly where I wanted to be. I worked with outstanding technology, highly capable colleagues and demanding customers. The expectations were high, the technical standards were clear and the environment rewarded competence, curiosity and disciplined problem-solving. I received consistently positive feedback from managers and customers. I was trusted with challenging assignments, and my career appeared to be progressing in the right direction. Professionally, things were going extremely well. My personal life was moving in the opposite direction. Two parts of life moving in different directions At the time, I was in a deeply unhealthy relationship. I will not turn this article into an account of another person or disclose private details that do not belong in a professional reflection. What matters here is the ...

Movie - Outcome (2026)

 

Movie - Apex (2026)

 

When Nobody Owns the Architectural Picture

Based on a LinkedIn post originally published on 6 February 2026 A few years ago, I joined a very large start-up to manage a DevOps team. The company’s product was extremely popular and clearly successful. The platform had grown rapidly to support increasing demand across several regions. As a newcomer, I asked what I thought was a straightforward question: Where is the architectural view of this environment? There was no clear answer. I then asked where I could find documentation explaining what existed, how the components interacted and how the platform was actually deployed. Again, there was no authoritative answer. Everyone understood a part It gradually became apparent that no one had a complete view of the system. Individual engineers understood their own areas. Application developers knew their services. Platform specialists understood particular infrastructure components. SREs knew the systems involved in the incidents they handled. Database specialists understood the data serv...

TV Serie - Memory of a Killer (2026) - Season 1

  Log Episode 1 - 2026-Feb-20 Episode 2 - 2026-Feb-20 Episode 3 - 2026-Feb-20 Episode 4 - 2026-Feb-20 Episode 5 - 2026-Feb-26 Episode 6 - 2026-Mar-03 Episode 7 - 2026-Apr-20 Episode 8 - 2026-Apr-20 Episode 9 - 2026-Apr-20 Episode 10 - 2026-Apr-20

Movie - Ready or Not 2: Here I Come (2026)

 

Movie - Brothers Under Fire (2026)

 

TV Serie - Childhood's End (2015)

  Log Episode 1 - 2026-Apr-16 Episode 2 - 2026-Apr-17 Episode 3 - 2026-Apr-18

Why I Chose iSCSI for the Back-End Storage Layer

Based on a LinkedIn post originally published on 4 February 2026 For the back-end storage layer of my home lab, I deliberately chose iSCSI instead of attaching every physical storage device directly to one host. This was not primarily a convenience decision. It was driven by architecture, scalability, resource isolation, maintenance and the need to keep failure behaviour understandable as the platform grows. In this design, storage devices are distributed across several back-end nodes. Those nodes expose block devices over iSCSI to HG000009, the front-end data store. HG000009 then aggregates and manages the storage through ZFS. The architecture can be represented conceptually as: Physical storage devices ↓ Back-end storage nodes ↓ iSCSI targets ↓ Dedicated storage network ↓ HG000009 iSCSI initiator ↓ ZFS storage control plane ↓ Client-facing storage services iSCSI is therefore more than a transport mechanism in this design. It creates a d...

Movie - His Girl Friday (1940)

 

Movie - Friday the 13th (2009)

 

Movie - The Mummy: Bride of the Dead (2026)

  Absolutelly bad. We stopped at 30 minutes in. Bad acting. Bad script.

Movie - Crime 101 (2026)

 

Movie - Project Hail Mary (2026)

 

Movie - Freeway (1996)

 

Movie - Shelter [UK] (2026)

 

When Experience and Organisational Readiness Do Not Align

Based on a LinkedIn post originally published on 2 February 2026 I recently closed a demanding professional chapter. The environment was fast-moving, high-pressure and ambitious. It provided exposure to substantial scale, organisational complexity and the realities of operating inside a large global company undergoing constant change. It was an intense experience, but also a valuable one. At the same time, it became increasingly clear that effort and expertise were not enough on their own. Successful leadership also requires alignment between the person, the mandate and the organisation’s readiness to use what that person brings. After open discussions and careful reflection, we concluded that continuing the collaboration was no longer the most constructive path for either side. These decisions are never easy. Sometimes, however, ending a professional relationship is more honest and responsible than preserving one in which expectations, operating models and long-term direction no longe...

TV Serie - Debris (2021) - Season 1

  Log Episode 1 - 2026-Apr-03 Episode 2 - 2026-Apr-03 Episode 3 - 2026-Apr-03 Episode 4 - 2026-Apr-03 Episode 5 - 2026-Apr-05 Episode 6 - 2026-Apr-05 Episode 7 - 2026-Apr-06 Episode 8 - 2026-Apr-06 Episode 9 - 2026-Apr-06 Episode 10 - 2026-Apr-07 Episode 11 - 2026-Apr-07 Episode 12 - 2026-Apr-07 Episodeo 13 - 2026-Apr-07

Movie - No Hard Feelings (2023)

 

When “Safe” Patching Still Bites

Based on a LinkedIn post originally published on 30 January 2026 While working in New Zealand, I supported a web-facing portal designed with strong redundancy. The environment included: local high availability; multiple portal nodes; production and disaster-recovery capacity; and remote replication between the primary and DR environments. From an operational perspective, it appeared to be an excellent candidate for rolling maintenance. Individual servers could be removed from service, patched and returned while traffic continued through the remaining nodes. As part of the regular security-maintenance cycle, we scheduled the deployment of a Solaris 10 patch. The process followed the expected progression: Laboratory environment. Development and test. Production. The patch behaved correctly in every non-production environment. We therefore proceeded to production. That was when the supposedly routine change stopped being routine. Starting with the lowest-risk node I began with the first s...