This is a great point. I will admit that, in the past, with certain tools that have command line interfaces and GUI interfaces, I have sometimes spent too much time trying to figure out how to do something through the GUI when I could've just done it with one or two terminal commands. But I didn't do it because the command line syntax felt obtuse to me, and I was resistant to learn it. But I would've solved the problem faster if I was not so stubborn (because I usually ended up having to complete the task... by doing it in the terminal anyway). In other words, my "sin" was not that I wasn't already adept at the command line. My "sin" was that I was stubborn and thus, I was working inefficiently.
With nearly any class of problem, I'm not so much concerned with whether you've already memorized how to fix it. I'm much more concerned with whether you know where-and-how to search for the answers (cuz that, in itself, is a skill). Noobs will burn a lotta time randomly clicking through poorly-focused google searches. For seasoned pros, even when they don't already have the solution in mind, they can leverage the internet as something like the 3rd lobe of their brain.
Some examples where command-line is more interesting to invest in:
Changing environment/ tools. If you're consultant learning command line pays off way better than using a GUI (company A requires everyone use IntelliJ, company B Visual Code)
No local development possible, no TTY on remote server: you can only use command-line.
If you're consultant learning command line pays off way better than using a GUI (company A requires everyone use IntelliJ, company B Visual Code)
I totally understand this point - although... my "answer" to this has been to not even consider opportunities anymore where the employer tries to dictate my toolset. I've had people contact me about Java opportunities, and then they tell me that, "The whole team is standardized on Eclipse." And... that's the end of the discussion for me.
I know that everyone doesn't have the same luxury. But I've actually run into this and I think it's borderline insane. After wrestling for years with Eclipse, and then seeing the night-and-day difference in writing Java in IntelliJ, I'm simply never writing another line of Java code in Eclipse again. If the employer thinks it's critical that I use the same IDE as everyone else on the team, then I am definitely not a good fit for that employer.
All that being said, I know that my little retort here is a diversion - and your central point is understood, and solid.
If the employer thinks it's critical that I use the same IDE as everyone else on the team
Then the employer is probably wondering why none of the top applicants end up taking the job and always end up picking the other company where the boss isn't micro-managing what socks they wear on thursdays.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
This is a great point. I will admit that, in the past, with certain tools that have command line interfaces and GUI interfaces, I have sometimes spent too much time trying to figure out how to do something through the GUI when I could've just done it with one or two terminal commands. But I didn't do it because the command line syntax felt obtuse to me, and I was resistant to learn it. But I would've solved the problem faster if I was not so stubborn (because I usually ended up having to complete the task... by doing it in the terminal anyway). In other words, my "sin" was not that I wasn't already adept at the command line. My "sin" was that I was stubborn and thus, I was working inefficiently.
With nearly any class of problem, I'm not so much concerned with whether you've already memorized how to fix it. I'm much more concerned with whether you know where-and-how to search for the answers (cuz that, in itself, is a skill). Noobs will burn a lotta time randomly clicking through poorly-focused google searches. For seasoned pros, even when they don't already have the solution in mind, they can leverage the internet as something like the 3rd lobe of their brain.
Some examples where command-line is more interesting to invest in:
I totally understand this point - although... my "answer" to this has been to not even consider opportunities anymore where the employer tries to dictate my toolset. I've had people contact me about Java opportunities, and then they tell me that, "The whole team is standardized on Eclipse." And... that's the end of the discussion for me.
I know that everyone doesn't have the same luxury. But I've actually run into this and I think it's borderline insane. After wrestling for years with Eclipse, and then seeing the night-and-day difference in writing Java in IntelliJ, I'm simply never writing another line of Java code in Eclipse again. If the employer thinks it's critical that I use the same IDE as everyone else on the team, then I am definitely not a good fit for that employer.
All that being said, I know that my little retort here is a diversion - and your central point is understood, and solid.
Then the employer is probably wondering why none of the top applicants end up taking the job and always end up picking the other company where the boss isn't micro-managing what socks they wear on thursdays.