JemmyThe PowerShell Manifesto Radicalized Me
medium.com/@sebastiancarlos/the-powershell-mani…
7 Comments
Comments from other communities
Let’s savor this one more time: Bill Gates walked into the meeting “riding high” because he acquired patents for malaria treatments. Reality beats satire every time.
DannyMacWho was “him” that Bill says was fucked?
Presumably whoever was in charge of .NET? Weird writing around that.
The podcast source transcript has more context. Apparently “him” was whoever was in charge of MSBNx, an unrelated, Bayesian Network thing, which Bill Gates was also obsessed with.
netvorThat sounds really evil, esp. if you already have low expectations and it’s not like I’m going to defend ol’Bill, but…
Do we know what he used the patents for?
Acquiring patent sounds like you want to use it as a gold mine by manufacturing the product for “best” price, which is pretty heinous, especially when it’s in conflict with saving lives. But in principle it could be the opposite. One could, entirely for altruistic reasons acquire a patent from someone with the intent to make the cure more affordable.
I mean, I don’t like Bill but let’s be honest, he’s no RFK Jr.
EezyvilleIf someone around you looks down on Indian developers, you can remind them that Windows became remotely usable thanks to AI… That is, “Actually Indians.”
Is that statement supposed to help Indians?
embed_meI think it’s playing on the joke that many ai companies will just lie about the ai and contract the work to actual Indians
Powershell (and nushell) is great. The concept of piping and manipulating objects instead of text is so comfortable. Having types is also great.
Administrating Windows would be a nightmare without it.
Bill Gates walked into the meeting “riding high” because he acquired patents for malaria treatments. Reality beats satire every time.
Bill Gates will never be a good guy.
Which Bill Gates got your attention? Epstein Island Bill or Embrace/Extend/Extinguish Bill? Either way, not a good look.
Good post. Definitely worth the read. Essentially: “how to convince execs who think they know more than they do that something is not only a good idea, but also their good idea”
The thing I never understood about PowerShell is that it’s partially more verbose than C#, which is one of the most verbose programming languages in existence. It just feels like you might as well go for a full-fledged programming language at that point.
The appeal of Bash et al is that the scripting is almost the same as the interactive usage, which you already know. But because PowerShell is so verbose, I’m really not sure people do use it interactively.
I guess, that code snippet in the article makes somewhat of a difference, in that PowerShell offers better features for interop between processes. But man, that still feels like it could’ve been a library instead…
PowerShell is fantastic in practice but whenever I think of writing shell scripts I think of bash first.
Bash is a lot more pleasant to work with overall, the biggest concern most people have is that it can be cryptic. IMO PowerShell scripts can be the exact same kind of voodoo.
Powershell is nice for scripting things close to the (windows) OS. But (granted I’m not exactly some PS wizard, I’ve just used it a few times for minor things at work) I agree it often feels unnecessarily verbose and cumbersome. For example the fact that you need to define a whole function to alias even just a single command with parameters. And just overall I find it very hard to read (though maybe that’s on the guy that did the powershell stuff before me, I don’t have great sample size here).
But I’ll take what I can get.
Warning: This article contains swearing (Quoted, from Bill Gates).
If you’re in IT and bad words offend you, fuck off. It’s a requirement.
Cevilia (she/they/…)This attitude is precisely why I didn’t end up in IT. :)
Medium.com radicalized me!
I love PS but lookup: Remove-MgIdentityAuthenticationEventFlowAsOnGraphAPretributeCollectionExternalUserSelfServiceSignUpAttributeIdentityUserFlowAttributeByRef
Is there a premium on hyphens?
in Powershell, yes. the cmdlet naming convention is Verb-CamelCase.
Only specific verbs are allowed as well. It works if the convention is broken, but it’ll complain when you import them as a module.
It’s fuzzy in my memory, but didn’t these all get auto-generated name s? I don’t think it was AI, this predates most of that, but there was some system they were using to auto-generate cmdlets
PS really is the bomb. Been a Windows sysadmin for a decade and I couldn’t do a damned thing without PS. I have no modern programming or scripting experience, yet picked up PowerShell and started implementing it very quickly. If you’re running Active Directory, it’s a must, no question.
Snover has some great intro to PS videos. That’s what got me started.
Fun read.