The most recent library I wrote for my team at work is painstakingly documented, and everyone has been invited to the multiple recorded training sessions.
They still act like it’s black magic and just push all work and questions to me.
Lol, welcome to the party. I’m not in a programming position, I’m on a systems engineering team. Most of my team mates can do some PowerShell scripting, but I have some programming classes under my belt.
I have a PowerShell script that is complex enough that I’m confortable calling it a program instead. Roughly half of the code is comments or logging the program flow. Every run generates a step by step log of all actions taken. I have 2 Word documents that summarize the process to different levels of detail, and a fucking flowchart for the visual peeps.
I’m still treated as the only person who could possibly flip the clearly labelled read only and route email to our team only switches and troubleshoot it.
To be fair, I recently learned during a vendor meet and greet that the vendor’s tech guy in the meeting had previously made a consulting firm to sell exactly what I built this program to do. Probably means I’m in the wrong line of work.
Yeah, you can actually run C# code “inline” in it without having to compile to an exe, which is simulataneously really cool, kinda janky in practice, a bad idea, and pretty cursed.
There’s definitely some weirdness with the syntax, and some odd footguns, but I’ve found those in most languages I’ve used for any considerable amount of time.
I work in an almost exclusively Windows environment, and the base version of PowerShell is preinstalled on all Windows stuff since I think Windows 7, with some really good integration with the Windows sysadmin tools. Not sure I’d reccomend it outside of that sort of environment.
The most recent library I wrote for my team at work is painstakingly documented, and everyone has been invited to the multiple recorded training sessions.
They still act like it’s black magic and just push all work and questions to me.
Lol, welcome to the party. I’m not in a programming position, I’m on a systems engineering team. Most of my team mates can do some PowerShell scripting, but I have some programming classes under my belt.
I have a PowerShell script that is complex enough that I’m confortable calling it a program instead. Roughly half of the code is comments or logging the program flow. Every run generates a step by step log of all actions taken. I have 2 Word documents that summarize the process to different levels of detail, and a fucking flowchart for the visual peeps.
I’m still treated as the only person who could possibly flip the clearly labelled read only and route email to our team only switches and troubleshoot it.
To be fair, I recently learned during a vendor meet and greet that the vendor’s tech guy in the meeting had previously made a consulting firm to sell exactly what I built this program to do. Probably means I’m in the wrong line of work.
Powershell is c# under the hood, no? It’s a pretty comprehensive programming language beyond anything bash does if you get down to it
I just can’t with the syntax though
Yeah, you can actually run C# code “inline” in it without having to compile to an exe, which is simulataneously really cool, kinda janky in practice, a bad idea, and pretty cursed.
There’s definitely some weirdness with the syntax, and some odd footguns, but I’ve found those in most languages I’ve used for any considerable amount of time.
I work in an almost exclusively Windows environment, and the base version of PowerShell is preinstalled on all Windows stuff since I think Windows 7, with some really good integration with the Windows sysadmin tools. Not sure I’d reccomend it outside of that sort of environment.