Well better than having comments that have nothing to do with the block of code following them.

And yes this happened even today.

I have tons of sample for enjoyment if you want :-)

@rutee07 not really being extremely blaspheme in front of the colleague.

Been there done that so I know what I am talking of 😃

@rutee07 wow really?

I would have enjoyed that! Not the colleague I guess but I would have definitely enjoyed it 😬

@devbf nah trust me it won’t...

@SortOfTested can definitely relate...

I only add that nobody ever reads the <put number here> pages of documentation I wrote coming to me with silly question/tickets which usually are answered with ‘it is documented on page x’...

@ilikeglue che lol so true yet I see horse of people swearing to the gods of code it is the ‘bestest (sic.) IDE’ in the world.

I had a funny discussion with a colleague about it the other day :-)

Ah VSCode has been renamed?

After reading this I think I am ready to switch career and finally fullfill my dream of owning a foodtruck making peoeple happy with my meals...

Thanks for giving me the motivation to finally give up IT.

@theKarlisK thanks I tried but don’t really like taste of bleach :-)

@Root true but how do I unlearn/unsee that.. that... well that?

@Stuxnet owe you for saving my poor dinosaur fingers some typing.

@heyheni I even have power down there and some food stored :-)

Just need to grab couple of raspberries and I am al set :-D

@nothappy what now you ever got that to work?

Hmmm We must be working for the same company

@devapsarl what they speak in Zurich is not German ;-)

@Wack Zürich c’est pas mal he l’adore :-)

Zürich/lLocarno here :-) Used to be in Neufchâtel before that

When I first "met" powerShell I was coming from a *nix background so felt really awkward but once I got the ropes of it I started appreciating it.

As my name implies I spend most of my time there and even use to automate the weirdest tasks in our environment (strong Azure/O365/MS shop) and to hook it up with obscure technologies building up automation "frameworks".

All in all I think we're pushing PowerShell past the limits of its design but as you said it's pretty neat to be able to use lower level stuff and leverage native .Net frameowrk functions.

As per the learning curve I think main issue, apart from some of its peculiarities, with it is a lot of admins/engineers need to switch their paradigm and start using paradigms which are "native" to devs but not to infrastructure people... which you can fully appreciate when checking SE's code :)

TLTR: I agree with your thoughts :)

*slowly raises hand*

@noyb Multi Factor Authentication or Two Factor Authentication, OTP or whatever you want to call it :)

@ShotgunSurgeon Lol guess I should start copying and pasting this :D I could do with another set of stickers from DevRant ;-)

By the way, this will be a full blown rant, I've just dropped my phone from literally 1 meter and despite it survived with no issues a 3 stories fall (long story) this time screen shattered...

Merry Christmas to me!

Hmmm this must be the same person who wrote the code I am refactoring these days (have an extensive rant with plenty of samples)...

F man.. I feel your pain!

Here we go for another round, I've already mentioned all variables have been configured with a global scope by default right?

Here's the best part.... let me calm down before I write this down.

All variables are 'sourced' from an EXTERNAL file which is stored in an obscure path, this per se could not be a bad thing what's really bad is that in every script "gloabl sourced" variable is assigned to a nother GLOBAL variable withiin the same script AND that "new" value is written back to the original Gloabl variable...

If you lost me up there don't worry, I'm lost as well and I'm reading this pice of monstrosity...

I'm revamping my CV and trying my fortune at McDonald's.

There is no amount of money they can pay me to endure this...

Here's another one that is too good to be passed.

Script is configured to log its operations, a good practices I thought, issue here being there are 3 different (yes THREE) functions used for logging... all three are doing the same exact thing, logging on the same exact file... just with different name. Not signature eh, completely different function NAME!

As added benefit, log file path is defined 4 times in the script... 4 times in different parts of the code for... well for no reason.

Time for the 9th coffee... and it's only 11:30am over here....

Day two of this torture, as I said many many gems to be discovered in this mess so let's start.

Just bit of contest for completeness, code is PowerShell and while I would have used C# given the complexity of the "thing" this is to be supported by infrastructure Engineers so... it is what it is.

- 4 and I say FOUR lines to declare a string variable containing.... *drum roll* a PATH!!!!! A FUCKING WINDOWS Path like C:\Script_Path\configFile.wtf for an obscure configuration file.

The best part of this? Path is, of course!, hardcoded making all of this very portable... but wait it is not over yet path does not exist on the server where this lives AND FILE IS NEVER IMPORTED!!!!!!

So I'm here looking at my screen asking myself WHY? WHY? WHYYYYYYYYYYYYYYY??????

Today I want to cry, craddle in a corner and cry even more, scream, did I say cry already?

@ShotgunSurgeon @Maer ahahha sure thing today I am going to continue with part two of this so stay tuned I am sure there are many other hidden gems just waiting for me!

And now ladies and gentlemen the good old try with a completely useless empty catch block!

How nice he was experimenting with new and unknown concepts!

P.S. Sorry for using this rant as a "blog" but it's nice to keep all together in one place so few months from now I can come back and check this.

This is getting better with the minute...

Literally quoting a comment:

# Pick the best object, but there should be only one

What the fuck does it mean "There should only be one"?

For the sake of God you're fetching data from a DB which is in turn populated by a fucking enterprise HR System and not in the fucking world two users can have the same Employee ID so... What the fuck does it mean "There SHOULD only be one?"

@Mr-Myrk I'm glad I'm not the only one with asimilar opinion.

The other day I was dealing with a Python solution, related to Adobe products, and made a similar comment in the office and I risked to be killed in place.

"How you dare offend Python!!!!!"

Why? WHY I always have to click and I knew this was coming and yet clicked the same!!!! WHYYYYYY?!?!