Not to sound like a jerk, but I would really like to see the math you used to determine that learning one text editor versus another increases your earning potential.
I might not have phrased that very well, I was trying to claim that being comfortable with command line tools (the unix "ide") will increase your earning potential as an engineer vs only knowing a gui ide.
Being familiar with command line tools for debugging allows you to troubleshoot issues in production, saving the company money, and troubleshooting issues in production generally means working with command line tools on linux servers. This is valuable even if you're not in operations.
2 examples to back this up (one from a backend developer and one from a frontend developer):
My former boss used to run the Customer Order Workflow (COW) team at amazon. He related to me how useless/slow he felt the first time a production issue popped up and he was trying to get some ungodly combination of WinSCP and notepad working. Obviously he learned vim very quickly after that.
Even if you're not on the "backend", you may find yourself needing to ssh to a server which is reverse proxing to something else, and running curl/wget to try and figure out why the CDN isn't serving the latest version of the CSS file you just created even though you're using a cache busting query string.
Sadly saving the company money doesn't always translate into more for you, but experiences like this generally end up making you a go to guy/girl, which can lead to being a lead engineer.
Being familiar with command line tools for debugging allows you to troubleshoot issues in production, saving the company money, and troubleshooting issues in production generally means working with command line tools on linux servers. This is valuable even if you're not in operations.
2 examples to back this up (one from a backend developer and one from a frontend developer):
My former boss used to run the Customer Order Workflow (COW) team at amazon. He related to me how useless/slow he felt the first time a production issue popped up and he was trying to get some ungodly combination of WinSCP and notepad working. Obviously he learned vim very quickly after that.
Even if you're not on the "backend", you may find yourself needing to ssh to a server which is reverse proxing to something else, and running curl/wget to try and figure out why the CDN isn't serving the latest version of the CSS file you just created even though you're using a cache busting query string.
Sadly saving the company money doesn't always translate into more for you, but experiences like this generally end up making you a go to guy/girl, which can lead to being a lead engineer.