other than first repliers I 'like' Powershell in combination with T-SQL, as my works often is managing files, analysing folder structures and building up connections and meta information in SQL-Server databases. It's often frustrating, to mask commands, to understand how to use the different constructs in the programming languages, ok! In most cases it ist although a reuse of code, that I created for other projects, so with all the help I got from other users and with some try and error, PowerShell makes it much easier for me to do my work.
It's sometimes the only way to do jobs, that need access to completely different behaving objects in Network. If you ever have become familiar with programming on objects, know DOS-commands as well as other Scripting languages, it's not a hard Job to adopt this knowledge to Powershell.
I think, that thare are much more spare time DBAs here, than fulltime DBAs. Most ones may have to do other Jobs as well and for all of their Jobs, they have to automate things. For this need, Powershell is helpful, as you can use one language beeing able to access also TSQL, filesystem, Active Directory, some user-Software,...
sorry for my poor "german" english 😉