<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Tulips, Windmills &amp; PowerShell: Dutch Scripting Guys</title>
	<atom:link href="https://dutchscriptingguys.com/feed/" rel="self" type="application/rss+xml" />
	<link>https://dutchscriptingguys.com</link>
	<description></description>
	<lastBuildDate>Sun, 30 Aug 2026 13:58:14 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1</generator>

<image>
	<url>https://dutchscriptingguys.com/wp-content/uploads/2024/10/cropped-Logo_vierkant-scaled-1-32x32.jpg</url>
	<title>Tulips, Windmills &amp; PowerShell: Dutch Scripting Guys</title>
	<link>https://dutchscriptingguys.com</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Understanding PowerShell Profiles: Customizing Your Environment</title>
		<link>https://dutchscriptingguys.com/understanding-powershell-profiles-customizing-your-environment-2/</link>
					<comments>https://dutchscriptingguys.com/understanding-powershell-profiles-customizing-your-environment-2/#respond</comments>
		
		<dc:creator><![CDATA[Casper Stekelenburg]]></dc:creator>
		<pubDate>Mon, 31 Aug 2026 06:00:00 +0000</pubDate>
				<category><![CDATA[Powershell]]></category>
		<category><![CDATA[Profiles]]></category>
		<category><![CDATA[Beginner]]></category>
		<category><![CDATA[PowerShell]]></category>
		<guid isPermaLink="false">https://dutchscriptingguys.com/?p=1377</guid>

					<description><![CDATA[Part 2: Building a Practical PowerShell Profile In the previous article, we created our first PowerShell profile and explored how PowerShell automatically loads a profile script whenever a new session starts. Now it&#8217;s time to make that profile useful. In this article, we&#8217;ll add common customizations that many PowerShell users rely on daily, including aliases, [&#8230;]]]></description>
		
					<wfw:commentRss>https://dutchscriptingguys.com/understanding-powershell-profiles-customizing-your-environment-2/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Understanding PowerShell Profiles: Customizing Your Environment</title>
		<link>https://dutchscriptingguys.com/understanding-powershell-profiles-customizing-your-environment/</link>
					<comments>https://dutchscriptingguys.com/understanding-powershell-profiles-customizing-your-environment/#respond</comments>
		
		<dc:creator><![CDATA[Casper Stekelenburg]]></dc:creator>
		<pubDate>Mon, 24 Aug 2026 06:00:00 +0000</pubDate>
				<category><![CDATA[Powershell]]></category>
		<category><![CDATA[Profiles]]></category>
		<category><![CDATA[Beginner]]></category>
		<category><![CDATA[PowerShell]]></category>
		<category><![CDATA[Quick Learnings]]></category>
		<guid isPermaLink="false">https://dutchscriptingguys.com/?p=1370</guid>

					<description><![CDATA[Part 1: Understanding PowerShell Profiles — Your Personalized Command-Line Workspace PowerShell is incredibly powerful out of the box, but one of its best features is often overlooked:&#160;PowerShell profiles. A PowerShell profile allows you to automatically configure your shell every time it starts. Think of it as a startup script for PowerShell. Instead of repeatedly defining [&#8230;]]]></description>
		
					<wfw:commentRss>https://dutchscriptingguys.com/understanding-powershell-profiles-customizing-your-environment/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Finding the Right ConvertTo-Json -Depth Automatically in PowerShell</title>
		<link>https://dutchscriptingguys.com/finding-the-right-convertto-json-depth-automatically-in-powershell/</link>
					<comments>https://dutchscriptingguys.com/finding-the-right-convertto-json-depth-automatically-in-powershell/#respond</comments>
		
		<dc:creator><![CDATA[Jos Fissering]]></dc:creator>
		<pubDate>Mon, 17 Aug 2026 06:00:58 +0000</pubDate>
				<category><![CDATA[Powershell]]></category>
		<category><![CDATA[Beginner]]></category>
		<category><![CDATA[Intermediate]]></category>
		<category><![CDATA[PowerShell]]></category>
		<guid isPermaLink="false">https://dutchscriptingguys.com/?p=1312</guid>

					<description><![CDATA[Learn how to calculate the maximum depth of a JSON object in PowerShell using a recursive approach. This article explains the logic behind the Get-JsonDepth function, discusses why arbitrary depth limits should be avoided, and explores the balance between accuracy, maintainability, and performance when traversing complex object graphs.]]></description>
		
					<wfw:commentRss>https://dutchscriptingguys.com/finding-the-right-convertto-json-depth-automatically-in-powershell/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>PowerShell Remoting over SSH: Managing Linux from the PowerShell Console</title>
		<link>https://dutchscriptingguys.com/powershell-remoting-over-ssh-managing-linux-from-the-powershell-console/</link>
					<comments>https://dutchscriptingguys.com/powershell-remoting-over-ssh-managing-linux-from-the-powershell-console/#respond</comments>
		
		<dc:creator><![CDATA[Jos Fissering]]></dc:creator>
		<pubDate>Mon, 03 Aug 2026 06:00:44 +0000</pubDate>
				<category><![CDATA[Powershell]]></category>
		<category><![CDATA[Intermediate]]></category>
		<category><![CDATA[PowerShell]]></category>
		<category><![CDATA[Troubleshooting]]></category>
		<guid isPermaLink="false">https://dutchscriptingguys.com/?p=1314</guid>

					<description><![CDATA[PowerShell Remoting over SSH combines the power of PowerShell with the universal availability of SSH. Especially in environments where both Windows and Linux systems are managed, it provides a modern and flexible way of working.]]></description>
		
					<wfw:commentRss>https://dutchscriptingguys.com/powershell-remoting-over-ssh-managing-linux-from-the-powershell-console/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>A way to Secure Credentials in Your PowerShell Scripts</title>
		<link>https://dutchscriptingguys.com/a-way-to-secure-credentials-in-your-powershell-scripts/</link>
					<comments>https://dutchscriptingguys.com/a-way-to-secure-credentials-in-your-powershell-scripts/#respond</comments>
		
		<dc:creator><![CDATA[Jos Fissering]]></dc:creator>
		<pubDate>Mon, 15 Dec 2025 06:00:00 +0000</pubDate>
				<category><![CDATA[Powershell]]></category>
		<category><![CDATA[Beginner]]></category>
		<category><![CDATA[Intermediate]]></category>
		<category><![CDATA[PowerShell]]></category>
		<category><![CDATA[Quick Learnings]]></category>
		<guid isPermaLink="false">https://dutchscriptingguys.com/?p=1287</guid>

					<description><![CDATA[Storing credentials in plain text within scripts is a common but risky practice. While it may seem convenient for automation, it exposes sensitive data to anyone with access to the code. In this article, we explore a safer approach using PowerShell’s ConvertTo-SecureString and ConvertFrom-SecureString to encrypt passwords tied to a specific user and machine. This method significantly reduces the risk of credential leaks while keeping automation seamless.]]></description>
		
					<wfw:commentRss>https://dutchscriptingguys.com/a-way-to-secure-credentials-in-your-powershell-scripts/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Scheduling PowerShell Scripts with PowerShell&#8217;s Scheduled Task Cmdlets</title>
		<link>https://dutchscriptingguys.com/scheduling-powershell-scripts-with-powershells-scheduled-task-cmdlets/</link>
					<comments>https://dutchscriptingguys.com/scheduling-powershell-scripts-with-powershells-scheduled-task-cmdlets/#respond</comments>
		
		<dc:creator><![CDATA[Casper Stekelenburg]]></dc:creator>
		<pubDate>Mon, 08 Dec 2025 06:00:00 +0000</pubDate>
				<category><![CDATA[Powershell]]></category>
		<category><![CDATA[Beginner]]></category>
		<category><![CDATA[Quick Learnings]]></category>
		<guid isPermaLink="false">https://dutchscriptingguys.com/?p=1283</guid>

					<description><![CDATA[When automating tasks on Windows, PowerShell scripts often handle the heavy lifting&#8212;but automation isn&#8217;t complete until those scripts run on their own. While many admins still use the graphical Task Scheduler, PowerShell provides a full set of cmdlets that make creating, managing, and automating scheduled tasks easier, faster, and more repeatable. In this guide, we&#8217;ll [&#8230;]]]></description>
		
					<wfw:commentRss>https://dutchscriptingguys.com/scheduling-powershell-scripts-with-powershells-scheduled-task-cmdlets/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>When Automation Goes Wrong: A Painful Lesson in PowerShell</title>
		<link>https://dutchscriptingguys.com/when-automation-goes-wrong-a-painful-lesson-in-powershell/</link>
					<comments>https://dutchscriptingguys.com/when-automation-goes-wrong-a-painful-lesson-in-powershell/#respond</comments>
		
		<dc:creator><![CDATA[Jos Fissering]]></dc:creator>
		<pubDate>Mon, 01 Dec 2025 06:00:00 +0000</pubDate>
				<category><![CDATA[Powershell]]></category>
		<category><![CDATA[Beginner]]></category>
		<category><![CDATA[Intermediate]]></category>
		<category><![CDATA[PowerShell]]></category>
		<category><![CDATA[Troubleshooting]]></category>
		<guid isPermaLink="false">https://dutchscriptingguys.com/?p=1276</guid>

					<description><![CDATA[Have you ever written a script that worked perfectly in testing, only to cause chaos in production? I have, and it was one of the most stressful days of my career.

This experience changed how I write scripts. More checks, fewer assumptions, and no blind trust in defaults.]]></description>
		
					<wfw:commentRss>https://dutchscriptingguys.com/when-automation-goes-wrong-a-painful-lesson-in-powershell/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Switch Statements in PowerShell: The Swiss Army Knife of Decision Making</title>
		<link>https://dutchscriptingguys.com/switch-statements-in-powershell-the-swiss-army-knife-of-decision-making/</link>
					<comments>https://dutchscriptingguys.com/switch-statements-in-powershell-the-swiss-army-knife-of-decision-making/#respond</comments>
		
		<dc:creator><![CDATA[Casper Stekelenburg]]></dc:creator>
		<pubDate>Mon, 24 Nov 2025 06:00:00 +0000</pubDate>
				<category><![CDATA[Powershell]]></category>
		<category><![CDATA[Intermediate]]></category>
		<category><![CDATA[PowerShell]]></category>
		<category><![CDATA[Quick Learnings]]></category>
		<guid isPermaLink="false">https://dutchscriptingguys.com/?p=1265</guid>

					<description><![CDATA[Switch statements in PowerShell are like the Swiss Army knife of control flow &#8211; they can handle multiple conditions with the elegance of a ballet dancer and the efficiency of a German engineer. Think of them as the sophisticated cousin of the if-else statement who went to college, learned multiple languages, and now works at [&#8230;]]]></description>
		
					<wfw:commentRss>https://dutchscriptingguys.com/switch-statements-in-powershell-the-swiss-army-knife-of-decision-making/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Enums in PowerShell: Strongly Typed Values for Robust Scripts</title>
		<link>https://dutchscriptingguys.com/enums-in-powershell-strongly-typed-values-for-robust-scripts/</link>
					<comments>https://dutchscriptingguys.com/enums-in-powershell-strongly-typed-values-for-robust-scripts/#respond</comments>
		
		<dc:creator><![CDATA[Jos Fissering]]></dc:creator>
		<pubDate>Mon, 17 Nov 2025 06:00:00 +0000</pubDate>
				<category><![CDATA[Powershell]]></category>
		<category><![CDATA[Advanced]]></category>
		<category><![CDATA[Deep Dive]]></category>
		<category><![CDATA[Intermediate]]></category>
		<category><![CDATA[PowerShell]]></category>
		<guid isPermaLink="false">https://dutchscriptingguys.com/?p=1267</guid>

					<description><![CDATA[Enums in PowerShell provide a clean way to work with strongly typed values, improving readability, maintainability, and reducing errors. By grouping related constants under a single type, you avoid magic numbers and hardcoded strings, gain autocompletion, and enable built-in validation in functions. Whether you use native syntax, Add-Type with C#, or classes with static properties, enums make your scripts more robust and easier to manage.]]></description>
		
					<wfw:commentRss>https://dutchscriptingguys.com/enums-in-powershell-strongly-typed-values-for-robust-scripts/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Dot Sourcing in PowerShell: The Art of Script Inclusion (Without the Drama)</title>
		<link>https://dutchscriptingguys.com/dot-sourcing-in-powershell-the-art-of-script-inclusion-without-the-drama/</link>
					<comments>https://dutchscriptingguys.com/dot-sourcing-in-powershell-the-art-of-script-inclusion-without-the-drama/#respond</comments>
		
		<dc:creator><![CDATA[Casper Stekelenburg]]></dc:creator>
		<pubDate>Mon, 10 Nov 2025 06:00:00 +0000</pubDate>
				<category><![CDATA[Powershell]]></category>
		<category><![CDATA[Intermediate]]></category>
		<guid isPermaLink="false">https://dutchscriptingguys.com/?p=1260</guid>

					<description><![CDATA[Dot sourcing is like the PowerShell equivalent of borrowing your neighbor&#8217;s tools &#8211; except instead of forgetting to return them, you get to keep everything permanently in your workspace. It&#8217;s a powerful feature that allows you to run a script in the current scope rather than in a new, child scope, making all its goodies [&#8230;]]]></description>
		
					<wfw:commentRss>https://dutchscriptingguys.com/dot-sourcing-in-powershell-the-art-of-script-inclusion-without-the-drama/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
