The PowerShell Podcast

Fresh off a PowerShell Wednesday session on Windows PowerShell versus PowerShell 7, Andrew Pla sits down with Ryan Yates, a longtime pillar of the UK PowerShell community and member of three PowerShell Working Groups (Cmdlets, Engine, and Interactive UX). Ryan pulls back the curtain on what working group members actually do, from triaging issues and reviewing PRs to deciding how bugs and enhancements should be implemented before the community picks up the work.
The conversation rewinds to Ryan's early days as an IT apprentice at Barclays, where supporting SharePoint without a Visual Studio license led him straight to PowerShell and a lifelong love of breaking things to learn how they work. Ryan also shares his take on PowerShellGet and PackageManagement headaches, why PSResourceGet and DSC v3 point to a better future, how AI's cost barrier affects everyday PowerShell users, and his dream of turning old devices into a local AI compute farm.
Things wrap up with a rapid-fire lightning round covering underrated cmdlets, favorite automatic variables, the most rewritten code block in PowerShell history, and a heartfelt call for more community eyes on the PowerShell repository.

Key Takeaways:

The PowerShell Working Groups triage issues and decide how bugs and enhancements should be handled, which opens the door for community members to step in and contribute the actual code.

PSResourceGet (Install-PSResource and Find-PSResource) is the path forward for module management, and cross-platform software installation is shifting toward DSC v3 rather than PowerShell itself.

Anyone can contribute. Start a discussion or open an issue in the PowerShell repository, and the team can convert between the two as needed. Everyone made their first contribution at some point.

Guest Bio:
Ryan Yates is a UK-based PowerShell community member who has been a driving force behind the UK and international PowerShell communities for over a decade. A former seven-time Microsoft MVP for PowerShell, Ryan currently serves on the PowerShell Cmdlets and Modules, Engine, and Interactive UX Working Groups, where he is in the PowerShell repository triaging, testing, and contributing. He began his career as an IT apprentice at Barclays supporting SharePoint, which led him to PowerShell, and he went on to help organize UK PowerShell user groups and PSDay UK. Ryan also helped keep the PowerScripting Podcast running in its later years. You can find him most days in the PowerShell Discord as pwshdoodUK.

Resource Links:

Ryan on GitHub: https://github.com/kilasuit

Sponsor Ryan on GitHub: https://github.com/sponsors/kilasuit

Ryan's Blog: https://blog.kilasuit.org/

Ryan on LinkedIn: https://uk.linkedin.com/in/ryanyates90

PowerShell Repository: https://github.com/PowerShell/PowerShell

PowerShell Working Group Definitions: https://github.com/PowerShell/PowerShell/blob/master/docs/community/working-group-definitions.md

PSResourceGet: https://github.com/PowerShell/PSResourceGet

DSC v3: https://github.com/PowerShell/DSC

ConsoleGuiTools (Out-ConsoleGridView): https://github.com/PowerShell/ConsoleGuiTools

Microsoft.WinGet.Client Module: https://www.powershellgallery.com/packages/Microsoft.WinGet.Client

PowerShell Discord: https://discord.com/invite/powershell

PDQ Discord: https://discord.gg/pdq

The PowerShell Podcast Hub: https://pdq.com/the-powershell-podcast

The PowerShell Podcast on YouTube: https://youtu.be/r5IYrhIEH4Y

Andrew sits down with longtime PowerShell legend James Brundage to recap what he calls his "summer of fun," a stretch of side projects that prove PowerShell can go way further than most of us ever thought to push it. James kicks things off with Wave, a module for creating and manipulating real .wav files in the object pipeline. Once you see audio as a sine wave and some math, you can generate notes, play music, and even draw animated SVG waves straight from PowerShell.
From there, the tour keeps rolling. MarkX turns Markdown into queryable XML so you can pull out code blocks or turn Markdown tables into typed data tables. James also shares how a vibe coded Wolfenstein 3D style clone in PowerShell (that got pulled from the internet after some tough feedback) sent him down the audio rabbit hole, and how he's collaborating with Bruce Payette on getting Braid to play nicely with PowerShell.

Then it gets visual. James walks through his Matrix module, which brings the transformation matrices already baked into .NET over to PowerShell and CSS, and shows off a hallway of fake 3D depth built entirely with PowerShell generated SVG. He explains the simple trick behind PowerShell static sites (a .html.ps1 script that spits out HTML, plus a ToString or HTML property on your objects) and shares Fun, a tiny web server where any function named with a leading slash becomes a web page. The episode wraps with a promise of a Part 2, because there is clearly way more to cover.

Key Takeaways:

PowerShell can do a lot more than most of us assume. Audio waveforms, Markdown as queryable data, matrix transforms, and fake 3D graphics are all fair game once you understand the small piece of math or tech underneath.

Static websites in PowerShell have been possible since version 1. Redirect output from a .html.ps1 script to a file, and add a ToString or HTML property to your objects so they render nicely on the web instead of dumping text in a terminal.

With the Fun module, naming a function with a leading slash turns it into a route on a local PowerShell web server, which makes web experiments quick and low stakes.

Guest Bio:
James Brundage is a former Microsoft engineer and one of the most prolific PowerShell developers around, known through his company Start-Automating and the handle MrPowerShell. He is the author of a long list of open source modules, including RoughDraft for multimedia work with FFMpeg, and he founded the PoshWeb GitHub organization to bring together open source PowerShell web development projects. James is currently heads down on creative projects around PowerShell web development, audio, and graphics.

Resource Links:
PoshWeb GitHub organization (open to new contributors) https://github.com/PoshWeb
Wave (work with wave files in PowerShell) https://github.com/PoshWeb/Wave
MarkX (Markdown, XML, and PowerShell) https://github.com/PoshWeb/MarkX
Matrix (matrix transforms with PowerShell, CSS compatible) https://github.com/PoshWeb/Matrix
https://www.powershellgallery.com/packages/Matrix
Fun (a fun functional PowerShell server) https://github.com/PoshWeb/Fun
James Brundage on GitHub https://github.com/StartAutomating
James Brundage's website https://MrPowerShell.com
Previous PowerShell Podcast episode with Bruce Payette on PowerShell and Braid https://pdq.com/resources/the-powershell-podcast/ep-82-exploring-powershell-braid-and-beyond-with-bruce-payette
The PowerShell Podcast on YouTube: https://youtu.be/WLEo6EjZqFM

Adam Driscoll, creator of PowerShell Universal, returns to the show for a deep dive into how AI has reshaped his day to day work. Since selling PSU to Devolutions last October, Adam has gone from writing thousands of lines of code himself to running a fleet of coding agents through GitHub Copilot, working across the PSU codebase, documentation, and Jira tickets. He and Andrew talk candidly about the personal side of that shift, the strange mix of mourning your old flow state while also getting more done than ever. From there the conversation turns practical, covering how Adam builds guardrails around agents using PowerShell modules and MCP servers, why planning in smaller steps beats one shotting a huge feature, and why Pester testing has quietly become non negotiable. They wrap with a PowerShell Universal 2026.3 update, including a redesigned admin console, new AI chat and MCP guardrail features, and Devolutions Agent support for running PSU jobs, plus a fun detour into Adam's side projects: a fully managed SQLite engine called Ahtola and an accidental 20,000 line Unity game.

Key Takeaways:

Treat your AI coding agent like a junior developer. It needs the "why" behind a task, not just the "what," or it will fill in the gaps with assumptions you don't want.

Guardrails matter more as agents get more capable. Adam constrains what his agents can touch by routing them through well defined PowerShell functions and MCP tools rather than giving them free rein, and tool approval settings let IT admins do the same in more sensitive environments.

Break big builds into small, reviewable steps instead of writing a massive plan and letting the agent run wild with it. Smaller steps mean you can actually review what changed at each stage.

Guest Bio:
Adam Driscoll is the creator of PowerShell Universal and joined Devolutions in October 2025, where he now leads its continued development. He's a longtime fixture in the PowerShell community, known for his tooling work and prolific output.

Resource Links:
https://ironmansoftware.com/

https://devolutions.net/

https://bsky.app/profile/adamrdriscoll.com

https://discord.gg/PDQ

The PowerShell Podcast on YouTube: https://youtu.be/u5zTzgEhWT8

Justin Grote (posh.guru) rejoins the PowerShell Podcast a year after his last appearance to talk about how fast the agentic AI world has moved since then. He walks through his experiments with the agent host protocol, running coding agents in isolated dev boxes and spot VMs so a stray command can only trash a container instead of his laptop. He and Andrew dig into what a "harness" actually is, how tools like these steer raw model output into something useful, and why that shift pushed Justin into a real existential dip this past summer, wondering what the point of hand building modules is when an agent can spin one up on demand. He works through how he came out the other side (doing it for the love of the game and the community), then gets into the practical stuff: a from-scratch C# rewrite of ModuleFast that cut Az module install time from seven seconds to three, the ExcelFast beta for slinging PowerShell objects in and out of Excel, and how he's tuning prompts using VS Code's new debug view and token caching. They also cover the rise of agent plugins (bundled skills plus MCP), his favorite lightweight plugin Ponytail, and Justin's read on where PowerShell fits once AI can talk to APIs directly. The conversation closes on advice for people getting into PowerShell right now and where to find Justin online.

Key Takeaways:

Agentic coding is moving fast enough that "harnesses" (the coordination layer around an LLM, like GitHub Copilot or Claude Code CLI) matter as much as the underlying model, and running agents in isolated dev boxes or spot VMs lets you hand over real autonomy without real risk.

Feeling threatened by AI generating modules on the fly is common right now. Justin's answer was to keep building for the love of the craft and the community rather than chasing relevance.

PowerShell's role is shifting from "the way you talk to a computer" toward a rapid prototyping and troubleshooting tool that both humans and AI agents reach for, especially anywhere a GUI or a full compiled language is overkill.

Guest Bio:
Justin Grote is a PowerShell MVP and the author of ModuleFast and ExcelFast, along with other tools in the PowerShell ecosystem like PoshNmap and several SecretManagement extensions. He works for a managed services provider and has been a fixture of the PowerShell community for years, known online as posh.guru.

Resource Links:
Justin Grote on GitHub https://github.com/JustinGrote
Justin Grote on Bluesky (posh.guru) https://bsky.app/profile/posh.guru
ModuleFast https://github.com/JustinGrote/ModuleFast
ExcelFast https://github.com/JustinGrote/ExcelFast
Ponytail (the agent plugin Justin mentioned) https://github.com/DietrichGebert/ponytail
PowerShell Discord https://discord.com/invite/powershell
The PowerShell Podcast on YouTube: https://youtu.be/MsgZoIKYnY0

Andrew welcomes back pen tester and AD security enthusiast Spencer Alessi (Tech Spence) fresh off DEF CON for a wide ranging chat on where PowerShell still fits into offensive security, how AI is changing his workflow, and what makes an environment genuinely painful to attack. Spencer talks through why PowerShell remains a favorite for both attackers and defenders, how he uses LLMs to speed up one off scripting tasks (and where they still fall short), and how he leans on AI tools to obfuscate offensive tooling during engagements. The conversation shifts into real world stories from the field, including a memorable case of exposed domain user hashes sitting on an overly permissive share, before wrapping up with the three controls Spencer sees make the biggest difference for defenders: application control, content filtering, and network segmentation.

KEY TAKEAWAYS:

PowerShell is still a top tool for both attackers and defenders because it is fast, flexible, and built into every Windows box, which is exactly why locking it down matters.

AI is great for offloading quick one off scripting tasks, but it often assumes intent incorrectly and can produce messy code, so manual review and hand written scripting still matter.

Application control, outbound content filtering, and network segmentation are the three controls Spencer sees make attackers' lives noticeably harder.

GUEST BIO:
Former Sysadmin, now Pentester @SecurIT360 | Microsoft MVP | Helping IT teams make their environment harder to attack | Social Media content & podcast @CyberThreatPOV

RESOURCE LINKS:
Spencer's website and newsletter: https://spenceralessi.com
 Spencer's link hub: https://links.spenceralessi.com
 Andrew's link hub: https://andrewpla.tech/links
 SecurIT360: https://securit360.com
 The Cyber Threat Perspective podcast: https://offsec.blog
 PowerSploit (offensive PowerShell framework): https://github.com/PowerShellMafia/PowerSploit
 Locksmith (AD CS misconfiguration finder, Spencer is a contributor): https://github.com/TrimarcJake/Locksmith
 ScriptSentry (Spencer's logon script scanner): https://github.com/techspence/ScriptSentry
 PDQ Discord community (PowerShell scripting channel): https://discord.gg/pdq
 PowerShell Wednesdays (weekly livestream): https://www.youtube.com/@PDQ
The PowerShell Podcast on YouTube: https://youtu.be/DDbBZqEJkSI