Re: Programming Languages Inflation...
20+ years, yep, that fits to my current main language.
Currently, simply due to "need by employers customer", I am using powershell since about 2019. I was programming in various languages from 1986 (Basic 3.5 on C16, soon ASM) until somewhere 1999, when I got employed somewhere where my coding skills were not recognized. Which led to a long pause of actual programming (beyond more or less complex .cmd or bash stuff with custom linux distro) for nearly 19 years. 2018 switch employer. Then, in 2019, it showed that those skills are still there when I started using PS (oder .NET-shell, which is more precise). I like powershell (v 5.1, always) for its simplicity, that you can tell variables from commands, and in a pinch you have the whole .NET, Windows .DLL calls and so on at hand. I rarely need a module, Posh-SSH is for now the only one I actually needed. Was able to do more than expected, including quite a number of things in AD where MS-documentation says "not possible in Powershell". Or PS examples calling compact.exe to use NTFS compression instead of "pure powershell" for some things. Calling compact.exe limit filenames since some characters don't work (like the & character), unicode and LONG filenames fail too.
C# would be the language I would be using when Powershell would be too slow for my need, but up to now I always found ways to get what I need. For example actually working serial modbus communication with Growatt and two Marsteks + 10 shellies for smart solar control. Or found ways to speed up a script by using .NET more directly instead cmdlets, in some cases a 20x speed increase over the previous variant.
I know there are tons of programmers out there better than me, including a lot being much better in Powershell. That does EXCLUDE Artificial Incompetence, since the questions I had are were never answered useful. I am happy to get my private stuff working so well, and at the same time using it as extended admin tool at work to get things done otherwise not possible, at least not in that timeframe... Actually classical "DevOpsAdmin", but I hate that buzzword DevOps since I see too many customers using it as an excuse to understuff IT and development with the "why two when one can do both" argument.