Sign in

SeeminglyScience

@seeminglyscience.com
220 followers 44 following 8 posts

Software Engineer for PowerShell at Microsoft

PostsRepliesMedia
SeeminglyScience @seeminglyscience.com · 22/12/2025
v2.4.0 of #PowerShell module ClassExplorer is released! New commands Invoke-Member and Get-AssemblyLoadContext github.com/SeeminglySci...
github.com
Release v2.4.0 · SeeminglyScience/ClassExplorer
2.4.0 - 2025-12-22 Invoke-Member (aka ivm) (#55) Quality of life command that makes interactive invocation of reflection info easier. Tracks source instance No need to save instances to an intermed...
1107
SeeminglyScience @seeminglyscience.com · 25/09/2025
Think he just meant he'd give me credit for embarrassing code. Jokes on him though, I'm perfectly capable of embarrassing myself 🙃
010
Reposted by SeeminglyScience
mdgrs @mdgrs.bsky.social · 29/04/2025
Do you know what bound and unbound script blocks are in PowerShell? I did not know but they are sometimes talked about in GitHub issues or in the community. If you are interested, check out my blog post from the past: mdgrs.hashnode.dev/scriptblock-...
An image showing two ways to create script blocks in PowerShell. One is defined with curly braces and the other is created from a string.
3156
SeeminglyScience @seeminglyscience.com · 22/04/2025
Use `Span<>`. Not in the cards though (outside of implicit conversion for method arguments)
020
SeeminglyScience @seeminglyscience.com · 15/01/2025
I'm definitely not suggesting the proliferation of the style choice, but I would also strongly recommend against someone removing said aliases in their profile.
010
SeeminglyScience @seeminglyscience.com · 15/01/2025
So I mention it only because it is much harder to completely write off when a decent chunk of folks do it regardless of what any one individual thinks. You can use github code search to gauge usage of each path:*.ps1 /\|\s*where [{a-zA-Z\-]/ path:*.ps1 /\|\s*where-object [{a-zA-Z\-]/
320
SeeminglyScience @seeminglyscience.com · 15/01/2025
While I personally agree, `where` and `foreach` specifically are not as unanimous in the community. There's a not insignificant group of folks who believe they should be treated more like keywords, and using the full command name is less readable. (Again, not me, just saying it's not as clear cut)
120
SeeminglyScience @seeminglyscience.com · 14/01/2025
ehhhh I don't know how much I endorse IDispatch, but IUnknown is neat
120
SeeminglyScience @seeminglyscience.com · 14/01/2025
One of these days you will see the glory of vtables. When you do, you'll finally feel complete and know true serenity. Through vtables, all things are possible (or maybe just virtual dispatch)
140
Reposted by SeeminglyScience
stevenbucher13.bsky.social @stevenbucher13.bsky.social · 13/01/2025
The #PowerShell and #openSSH community call is this Thursday 9:30am PST! Add any topics you'd liked covered in this discussion github.com/PowerShell/P...
github.com
January 16th 2025 Community Call · PowerShell PowerShell · Discussion #24768
Agenda AI Shell Preview @StevenBucher98
0109
Reposted by SeeminglyScience
mdgrs @mdgrs.bsky.social · 13/01/2025
If your #PowerShell module loads dlls that are widely used by other modules, it's a good practice to implement ALC (Assembly Load Context) so that the right version of dlls are always loaded. Here is how I learned about PowerShell ALC:
1124