Conversation

Something that melts my brain on a daily basis is that due to reasons, about 80% of the 'code' my team writes is #PowerShell scripts (don't ask). #VSCode is actually a good environment for this, because it has some pretty decent built in best practice analysis, like it will alert you if you have an unreferenced variable, an uncalled function, deprecated syntax, excess loops, &c. Very rookie code hygiene stuff, but useful.

The quality of content my team has been making with VSCode has been pretty good.

But now I have a couple of guys that are using #Copilot to make scripts.

So I take the code they had Copilot "write" and open it in the normal-ass VSCode ISE to proofread it.

And the goddamn thing lights up like a Christmas tree, because the Microsoft product that "wrote" the code did not follow any of... the Microsoft product that you use to edit the code's best practices.

I hate it here.

#IT #SysAdmin #DatacenterLife

I have one dude who, and I don't know why it's only him, keeps turning in scripts that have a ~400 line function to easily change the console output font color to any of the possible colors despite it being uncalled because his script has no console output.

Me explaining why the vibe coders were all found face down in my swimming pool

#IT #SysAdmin #DatacenterLife