• 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’s time to make that profile useful. In this article, we’ll add common customizations that many PowerShell users rely on daily, including aliases, module imports, environment variables, and PSReadLine enhancements. Why Customize Your Profile? The goal of a PowerShell profile is simple: eliminate…

  • 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: 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 aliases, importing modules, or tweaking your prompt, you can save those customizations in a profile and have them loaded automatically.…

  • 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.

  • 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.

  • 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.

  • 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.

  • Switch statements in PowerShell are like the Swiss Army knife of control flow – 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 a consulting firm. While if-else chains are like asking “Are you this? No? How about this? No? This?” until you…

  • 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.

  • Hashtables and PSCustomObjects may look similar in PowerShell, but they serve very different purposes. This post explores their syntax, performance, and practical use cases, helping you choose the right structure for dynamic data handling or clean output formatting.

  • Choosing between -match and -like depends on the complexity of your pattern matching. Use -like for simple wildcard checks, such as finding strings that contain certain characters (* and ? are your friends). When you need more power, like anchoring patterns, grouping, or advanced conditions, reach for -match, which leverages regular expressions. In short: -like is quick and simple, -match is precise and flexible.