The writing style in AI generated text is unmistakably non-personal and boring. With more content (posts, blogs, code) being made by AI I fear more people will attempt to mimic the same style.

Let's not forget to have room for personality, flair, linguistic diversity and typos.

Everyone so excited about MCP as the latest AI awesome sauce

Me: looks like an API gateway

@monkchips.com: SOAP for AI tools cool cool

Time to answer all the same questions again

Thanks! Feel free to create an issue or a PR if you come across anything that doesn't work or should be improved 😉

and I managed to sneak in a fun little excercise in subnet math 🤓

Link to the PowerShell function here: github.com/matsest/gh-r...

..and I've added some nicely formatted output with URLs to #Azure and #GitHub 🪄

Billing is more or less static since it does not scale to zero. So not much different from a small VM in my experience.

Depending on your usecase I would consider Container Apps. More batteries included, better scaling up and down and with a more usage based billing.

I partly understand it, coming from a Linux background myself, but in total I agree with you, especially on cmdlet names. Super useful!

Personally I see it in a CLI setting. Would love to have more use of long+short-form parameter names for cmdlets, similar to --name/-n, --silent/-s etc.

That's also a good tip! Variable validations are great!

A feature too rarely used in a lot of PowerShell code i see around.

...and third maybe due to the very verbose syntax, especially for those utilizing it mostly for interactive command line shells.

(although aliases is underutilized in PowerShell as well! - bsky.app/profile/jsno...)

That's a good point - it's a much better check to use that method in this case.

I often tend to use typed variables, as PowerShell can be a bit too relaxed with implicit type conversions, but it's too bad that script analyzer don't pick cases like this stuff up, and no runtime warnings is printed.

From the docs: "But PowerShell is very generous and allows for variables to be any type. If you decide to strongly type a value type, it cannot be $null. PowerShell converts $null to a default value for many types."

IMO PowerShell is too generous in these cases! 😁