Prompt Engineering as Code: AI Memory Transfer and Reusable Instructions IntroductionIn the rapidly evolving field of artificial intelligence, efficiency and consistency are paramount. Borrowing from the successes of methodologies like Infrastructure as Code (IaC) and Documentation as Code (Docs as Code), we can enhance AI interactions by treating prompts and context as code artifacts. This approach introduces two innovative concepts under one banner: Prompt Seed: Capturing and transferring AI interaction contexts in code format.

Generation GovTech IntroductionThis post introduces a new term, Generation GovTech, or GenGT for short. You’ll find a full description of this term below. To explain it fully, we’ll first cover the recruitment campaign by the Dutch Ministry of Defense: Generation D Generation DIn 2022, the MoD launched the recruitment campaign Generation D. The campaign aimed to attract people with a specific mindset. This mindset includes individuals who want to do meaningful work, believe in cooperation, and seek personal growth.

Co source Intro Protected Inner Source RecapProtected Inner Source is a source code sharing strategy that defines an intermediate model between Open Source and Inner Source. The analogy used here is that C# Access Modifiers define a ‘Protected Internal Class’ as an intermediate between ‘Public Class’ and ‘Internal Class’. The purpose of which is to be more closed off between assemblies than ‘Public Class’, yet more open for reuse than ‘Internal Class’.

Protected Inner SourceUPDATE: Based on feedback, I am changing the name of this source code sharing strategy to ‘Co Source’. The direct analogy between Protected Internal Class and Protected Inner Source seemed to imply a lack of security in traditional Open Source sharing strategies, which was not my intent. Read more about the naming change in my follow-up article here: Co Source - Renamed Source Code Sharing Strategy Intro Inner sourceIn the digital era, software development is a cornerstone of innovation.

Firewall port testing IntroRecently I had some issues at a customer project where, due to the complexity of the environment, sometimes firewall ports were closed after they had initially been added to the rules list. This caused unexpected errors for SharePoint, of which we were unaware at the time that these were due to firewall issues. While analyzing the issue I came across the Test-NetConnection PowerShell command, which I used to manually verify the issue on one server.

SharePoint ULS Empty log filesRan into an annoying issue today where a SharePoint server was not writing trace log messages, the result was a log directory with 0 bytes logging files. Incidentally I found a Event Log error with the code: “A Session “WSSUSAGESESSION15” failed to start with the following error: 0xC0000022” Other posts mention adding the service account (or the WSS_WPG group) for the ‘SharePoint Tracing Service’ Windows Service to the administrators group, tested that, this indeed fixes the problem.