4 ms·
When I quit my prior job, they started a multi-month project to replace all of my PowerShell with "proper" C#. Then they decided it was too hard, threw it all
by sqldba 11y ago
When I quit my prior job, they started a multi-month project to replace all of my PowerShell with "proper" C#.
Then they decided it was too hard, threw it all away, and just decommissioned parts of the application and run everything else manually.
Working under brilliant minds like that you can see why I quit.
- yardie 11y agoSounds like a bunch of C# devs who didn't know Powershell and couldn't be arsed to learn it. Even though it has similar syntax. To some developers every problem requires the only hammer they have. Must have been really bad. Why not just hire you on as a consultant?
- JBReefer 11y agowhich is sad, because Powershell is great
- voltagex_ 11y agoI'm not fantastic with Powershell but there's another potential reason: you're not allowed to run "random" exe files on $SERVER but (signed) Powershell scripts are fine. I'm not sure where the cutoff point is between this needs to be an app / this can stay as a script, but Powershell seems to lend itself to going either way. I can either incrementally replace C# functions with Powershell (while importing types and functions that I need) or incrementally replace Powershell with C# with the same method.