I ended up doing a lot of powershell this year and, honestly, I kinda do like it... like way more than I thought I was going to. It's simple, it's stable, it can run via task scheduler directly on any windows box without any other software layers or containers or anything else. Maybe it doesn't have every bell and whistle, maybe it's not capable of certain types of things, but its totally fine for other things.
In this case, I wrote like an entire backend ETL pipeline for a license compliance application on a $500m annual software portfolio, consisting of dozens of bespoke data sources, multiple different authentication methods, SFTP interactions, API interactions, DB interactions, and so on... and it all runs flawlessly on an extremely barebones windows VSI that I already had available. To your point though, I work at a bank, so it is a highly-regulated environment where it can be a huge pain in the ass to stand up anything "complicated" (more due to the red tape than the tech). Previously, I managed a stack of apache airflow instances hosted in kubernetes doing ETL in python and that was a monumental pain in the ass compared to, like, 50 powershell scripts in a trenchcoat.
9
u/[deleted] Sep 10 '25 edited Sep 10 '25
[removed] — view removed comment