Gilbert Sanchez (💻 HeyItsGilbert)
banner
gilbertsanchez.com
Gilbert Sanchez (💻 HeyItsGilbert)
@gilbertsanchez.com
610 followers 310 following 370 posts
Staff Software Development Engineer. Formerly known as the "Señor Systems Engineer" at Meta. Preaching the value of #PowerShell, #DEI, and #DevEx. Always interested in Systems Thinking, Cognition, and Learning in Public. 📸 Banner by jtkyber1
Posts Media Videos Starter Packs
Pinned
When I see someone hate on PowerShell it has, so far, always been because they misunderstand what it can do. That or they hate the syntax. Syntax style is kind of understandable if you prefer terse languages. But when you see the hate, just realize it comes from ignorance more than anything.
FYI it's literally `irm wled.local/json%60 post with a body of `{'ps': 1}`. I'm definitely going to be using more WLED API.

Hmm.. what about a "progress bar" for the meeting.
wled.local
Thank you so much for this opportunity... /grumbling
Reposted by Gilbert Sanchez (💻 HeyItsGilbert)
I've published a new issue of Behind the PowerShell Pipeline: PowerShell Temporary Work

Become a premium member to read the entire article and get access to the catalog of content going back to 2022. #PowerShell

PowerShell Temporary Work
buttondown.com
Sometimes I forget how much of a nerd I am. I got very excited during a team meeting this morning when my #PowerShell meeting notification script was able to flash the LED strip under my monitor via #WLED. When I have a meeting in <5m my monitor does a slow red flash.
I’m excited to share that I’ll be speaking at @powershellsummit.org 2026!

1. From Burnout to Built-to-Last: The Open Source Org Advantage
2. Markdown Madness: Static Sites for Fun & Profit

Two topics I'm super passionate about!

If you’re headed to #PSHSummit, let’s connect!
Cool. Chatted with Marius who owns this now. He delisted the latest version. I suggested bumping major version just to be safe. I look forward to seeing improvements 💜
Looks like the current version is just a template that is missing any actual code. Coming from github.com/PSModule/Jwt where the original was coming from github.com/SP3269/posh-.... I have no idea how this could have happened.
Gallery:
www.powershellgallery.com/packages/JWT...
JWT 1.9.1
PowerShell module to create and verify JWTs, the JSON Web Tokens
www.powershellgallery.com
Uh... Was looking at the JWT PowerShell module. Noticed it was updated 18hrs ago, went to checkout the changelog... but the repo hasn't been updated in 4 years... Something smells fishy...
There are 2 people in this world: Those who hear Suburban Home and (correctly) scream along, and everyone else. www.youtube.com/watch?v=x9PP...
Suburban Home
YouTube video by Descendents - Topic
www.youtube.com
100% this. Maintaining backwards compatibility is a huge burden and one that can't (and shouldn't) be shirked. This is what it means to support enterprise software.
That has been the first legitimate set of criticisms about PS I've seen on bsky. I can't disagree with most of this (especially around package management). I would say Pester has a learning curve.
The alternative to a restricted terminal would be worse. Think of launching as Administrator like using sudo (you can even use gsudo to do the same). Now imagine if ~~everyone~~ everything had sudo access.
For a second I thought this was saying that WMI was going! If you're moving to PowerShell, use the CIM commands where possible!
📌 Microsoft to Remove WMIC in Windows 11 25H2, Pushes PowerShell Adoption https://www.cyberhub.blog/article/13255-microsoft-to-remove-wmic-in-windows-11-25h2-pushes-powershell-adoption
Microsoft to Remove WMIC in Windows 11 25H2, Pushes PowerShell Adoption
Microsoft has announced the removal of the Windows Management Instrumentation Command-line (WMIC) tool in Windows 11 version 25H2 and later releases. This decision follows Microsoft's 2021 announcement that WMIC was deprecated and would be replaced by PowerShell. WMIC has been a staple for system administrators, enabling command-line management of Windows systems through WMI. Its removal underscores Microsoft's shift towards PowerShell, which offers more advanced scripting and automation capabilities. The deprecation of WMIC has significant implications for cybersecurity professionals. Many scripts and tools that rely on WMIC for system queries, management tasks, and automation will need to be updated to use PowerShell cmdlets. This transition may pose challenges for organizations with extensive WMIC-based scripts, but it also presents an opportunity to adopt more modern and secure practices. PowerShell's robust features, including better integration with security tools and enhanced scripting capabilities, can improve operational efficiency and security posture. For cybersecurity professionals, this change highlights the importance of staying current with Microsoft's evolving toolset. It is crucial to review and update existing scripts and tools to ensure compatibility with PowerShell. Additionally, this transition may impact security monitoring and incident response workflows that rely on WMIC. Organizations should plan for this change by testing PowerShell alternatives and updating their documentation and training materials accordingly. In conclusion, while the removal of WMIC may cause some disruption, it aligns with Microsoft's broader strategy to modernize Windows management tools. By embracing PowerShell, cybersecurity professionals can leverage its advanced features to enhance their system management and security operations.
www.cyberhub.blog
Yea, you're not wrong. I never just open a result from the search. I usually have to dig into things to see what's going on and that almost always means going to the (hopefully configured) repo link.
I don't disagree that the PSGallery leaves a lot to be desired, but what do you see from GitHub that would make you prefer it? I mean I definitely go from PSGallery to GitHub to review what the code does, etc. But I don't think I've ever found the GH package experience that great.
Reposted by Gilbert Sanchez (💻 HeyItsGilbert)
The wait is over! PowerShell Weekly for September 5, 2025 has just been published. Dive into the latest insights and scripts to make your life easier.
psweekly.dowst.dev?p=8174
#PowerShell #Automation #TechNews
DOWST.DEV | September 5, 2025
psweekly.dowst.dev
I'd love to hear what you have in mind.
- Handle the gotchas like undefined locales on Ubuntu with smart fallbacks that keep your modules working everywhere
- Stop making non-English speakers struggle through your docs - your tools should adapt to users, not the other way around
- Learn PowerShell's Import-LocalizedData magic - it's easier than you think to support multiple languages with PSD1 files
- Build a bulletproof localization pipeline using YAML sources, Crowdin for community translations, and automated PSD1 generation