You’re likely here because you have a question. You might even be frustrated. I’m dropping in to just let you know you got this, and more importantly: learning this WILL matter, so the time spent on this is not wasted.
Short story to back this up: I started pushing PowerShell hard when Exchange 2007 took the leap and it became impossible to configure a server farm unless you knew it. A fwe years later DSC was announced and I was all in. Few year after that? I left all Microsoft related work and supported a pure Linux/AWS/Container/serverless farm for 2 years. Wait … what? Yeah … stopped PowerShell entirely. But you know what?
Learning a language like PowerShell that is so far beyond simple DOS/BASH scripts meant learning things like Python was easier. The concepts of structuring your code, testing with pester, all f it translated well into a Linux world. Then something crazy happened.
Someone in another department was trying to figure out how to convert their mess of old scripts to work with ansible, packer and other modern cloud tools. There’s something wonderfully easy about the PowerShell verb model … I was able to crank out a simple server deployment in an afternoon. The commands were easy to pick back up (get-verb… oh yeah), and the further knowledge I gained from coding in Python and Go easily translated back to making even higher quality code in PowerShell. So even though I basically abandoned Microsoft for awhile … it continued to pay dividends.
It’s WORTH IT. You’re not just learning a new way to script. You’re learning a programming language, and in this developers first world that is invaluable. Keep at it, whoever you are. No matter how much that current PowerShell project must suck … you got this. And it will pay back.