Earlier quoted context omitted.
> One would hope, but alas! Perl was notorious for being write-only back in the day. I don't agree that's a valid rebuttal, as the operative word is the weasel copout "know what they are doing". > PoSh is closer to read-only for most devs. A read-only language is a language with a serious expressiveness problem. In contrast with, say, Python, which you need to go way out of your way to write code that's hard to under…
>the weasel copout "know what they are doing" Let's try a precise quality comparison, more for fun than anything. We have established someone knowing what they're doing makes any comparisons meaningless. I imagine you would agree with me that someone who "only kind of knows what they are doing" is even less helpful (what do they know? what do they not know?). So our last option is someone who does not know what they'…
These people just went from "never programmed before" to "knowing how to program" - I doubt people that made an investment like this would "stop to the first tool" because "it works". Sure, they might not rewrite something that works, but they would wonder "is there a better tool to do the job?"
You can of course target "what is the minimum I can do on this and then be able to focus on my job" and never worry about other issues (could I have done more? could I have done better? is it extendable? is it maintainable? etc.) but that is more about how you view "your job". If you are a doctor and your job is "heal patients" then learning another programming language is not your job. If you are someone maintaining some tool written in a specific language, then learning another programming language is not your job. If you are a software engineer that can solve multiple problems, wondering if you should know another programming language is part of your job.