My things

  Log Episode 1 - 2026-Jun-21 Episode 2 - 2026-Jun-21 Episode 3 - 2026-Jun-21 Episode 4 - 2026-Jun-21 Episode 5 - 2026-Jun-21 Episode 6 - 2026-Jun-21 Episode 7 - 2026-Jun-21 Episode 8 - 2026-Jun-21 Episode 9 - 2026-Jun-21 Episode 10 - 2026-Jun-21 Episode 11 - 2026-Jun-22 Episode 12 - 2026-Jun-22 Episode 13 - 2026-Jun-22 Episode 14 - 2026-Jun-22 Episode 15 - 2026-Jun-22 Episode 16 - 2026-Jun-22 Episode 17 - 2026-Jun-22 Episode 18  [1992-Mar-31] - 2026-Jun-29 Episode 19 [1992-Apr-07] - 2026-Jun-29 Episode 20 [1992-Apr-14] - 2026-Jun-29 Episode 21 [1992-Apr-28] - 2026-Jun-30 Episode 22 [1992-May-12] - 2026-Jun-30

 Log Episode 1 - 2026-Apr-19 Episode 2 - 2026-May-03 Episode 3 - 2026-May-03 Episode 4 - 2026-May-11 Episode 5 - 2026-May-17 Episode 6 - 2026-May-31 Episode 7 - 2026-Jun-07 Episode 8 - 2026-Jun-17 Episode 9 - 2026-Jun-22 Episode 10 [2026-Jun-28] - 2026-Jun-29

 

  What an analogy about what is happening today in the UK!!!!!

 

Log Episode 1 - 2026-Jun-24 Episode 2 - 2026-Jun-24 Episode 3 - 2026-Jun-24 Episode 4 - 2026-Jun-24 Episode 5 - 2026-Jun-24 Episode 6 - 2026-Jun-24 Episode 7 - 2026-Jun-24 Episode 8 - 2026-Jun-24 Episode 9 - 2026-Jun-24 Episode 10 - 2026-Jun-25

  Log Episode 1 - 2026-Jun-21 Episode 2 - 2026-Jun-21 Episode 3 - 2026-Jun-21 Episode 4 - 2026-Jun-21 Episode 5 - 2026-Jun-21 Episode 6 - 2026-Jun-21 Episode 7 - 2026-Jun-23 Episode 8 - 2026-Jun-23 Episode 9 - 2026-Jun-23 Episode 10 - 2026-Jun-24

Based on a LinkedIn post originally published on 2 March 2026 Job searching frequently teaches lessons that extend far beyond technical interviews, CVs and role requirements. Every recruitment process is also a communication system. It contains participants, handovers, identities, schedules, decisions and dependencies. When any of those elements remains ambiguous, misunderstandings become increasingly likely—even when everyone involved has good intentions. I recently experienced a hiring process that illustrated this clearly. One opportunity, two company names The vacancy was advertised under one company name, but all subsequent communication arrived under another brand belonging to the same corporate group. From inside the organisation, the relationship between those brands was probably obvious. Employees and recruiters would already understand the group structure and know which teams operated under which names. From a candidate’s perspective, however, the connection was not immediate...

 

 

  Log Episode 1 - 2026-Jun-16 Episode 2 - 2026-Jun-16 Episode 3 - 2026-Jun-17 Episode 4 - 2026-Jun-17 Episode 5 - 2026-Jun-18 Episode 6 - 2026-Jun-18 Episode 7 - 2026-Jun-18 Episode 8 - 2026-Jun-18 Episode 9 - 2026-Jun-18 Episode 10 - 2026-Jun-18 Episode 11 - 2026-Jun-19 Episode 12 - 2026-Jun-19 Episode 13 - 2026-Jun-19 Episode 14 - 2026-Jun-19 Episode 15 - 2026-Jun-20 Episode 16 - 2026-Jun-20 Episode 17 - 2026-Jun-20 Episode 18 - 2026-Jun-20 Episode 19 - 2026-Jun-20 Episode 20 - 2026-Jun-21 Episode 21 - 2026-Jun-21 Episode 22 - 2026-Jun-21

 

  My views Plot After a night of drunken partying,  Tree Gelbman  wakes up on her birthday in the dorm room of classmate Carter Davis. She dismisses him, returning to her room. Her  sorority  housemate Lori Spengler gives her a cupcake, which she throws away. Tree meets with her married professor, Gregory Butler, with whom she is having an affair. That night, on her way to a party, Tree is lured into a tunnel and murdered by a figure wearing a mask. She immediately wakes up back in Carter's bed and is unnerved to find the previous day's events repeating themselves. Baffled, she relives the day, this time avoiding the tunnel and reaching the party. However, the masked killer follows her and murders her again. Tree again wakes up in Carter's bed, realizes she is in a  time loop , and barricades herself in her room to avoid death. The killer, already hiding inside, murders her a third time. Waking up, Tree explains the events to Carter. He suggests taking adva...

 

Based on a LinkedIn post originally published on 27 February 2026 In the 1990s, while living in north-eastern Brazil and running my own business, I was invited to visit the customer of one of my existing clients. The introduction came through word of mouth. Referrals were particularly valuable at the time, so I agreed to make the journey. The site was almost two hours away by car. When I arrived, I found a large factory that supposedly produced soap and similar products. We walked around the premises, and almost immediately something felt wrong. There was no single dramatic piece of evidence. Instead, there was a collection of details that did not form a coherent picture. Several parts of the factory appeared abandoned. Production areas were unusually quiet. The site contained some activity, but it lacked the rhythm expected of a functioning industrial operation. People in the cafeteria were eating from aluminium packages. The apparent scale of the business did not match the conditions...

 

Log Episode 1 - 2026-Apr-13 Episode 2 - 2026-Apr-14 Episode 3 - 2026-Apr-19 Episode 4 - 2026-Apr-23 Episode 5 - 2026-May-30 Episode 6 - 2026-Jun-02 Episode 7 - 2026-Jun-02 Episode 8 - 2026-Jun-11

Based on a LinkedIn post originally published on 25 February 2026 The network architecture of my home-lab platform is deliberately segmented and role-specific. Each network exists to serve one clearly defined purpose, and the physical and logical design reinforces that purpose. The objective is not simply to provide connectivity. It is to make traffic paths, failure modes and security boundaries predictable. The central design rule is simple: each interface has one purpose—and only one. HG000009, the platform’s front-end data-store node, participates in three different network roles: back-end storage connectivity; front-end access for systems consuming shared storage; and administrative access through a dedicated management network. These roles have different performance, availability and security requirements. Combining them onto an undifferentiated network would obscure those differences and make the resulting system harder to understand and operate. The high-level topology Back-en...

 

 

 

 

Based on a LinkedIn post originally published on 23 February 2026 In the 1990s, I was hired for a short engagement at a regional telecommunications company. It was my first practical exposure to a mainframe-based production environment—something I understood in theory but had never previously worked with directly. My primary assignment was to update a large number of COBOL programs in preparation for the Year 2000 problem. COBOL was new to me, but learning the language was not the most difficult part. Previous experience with other programming languages made it relatively straightforward to understand the syntax, program structure and processing logic. The more interesting challenge was learning how the entire production environment behaved around the programs. The program was only one part of the processing time As I became familiar with the mainframe environment, I noticed that some data-processing tasks took a considerable amount of time to complete. The delay was not necessarily ca...