I've always been a nano-pleb when it came to shell-editors. Somehow I never grew fond of Vim or Emacs.
Linux - Even after switching to macOS for mobile development, I still can use most commands here
Git - While I had a short stint with CVS, I basically used Git my whole career
SSH - I don't know too much about it, but I stopped using FTP after I found out about SSH on my first job
JavaScript - I did C at high school, C++ and Java at university and VBA and PHP in my first jobs, but since I started JS 7 years ago I use it for everything
Photoshop - I never was much of a PS-pro, but my PS skills somehow have proven quite timeless and useful for over 10 years now, even when using GIMP
Reading code - sounds obvious, but after switching to JavaScript all libraries and frameworks I used where open source, so I could read the code instead of asking on StackOverflow
Asking people why - often I tend to simply write down feature requests and try to blindly implement them, asking people why they need them often reveals that they are requesting the wrong thing.
How I understood was that basics of OS (linux), source control (git), security (SSH), language (javascript), etc will have a lasting impact throughout one's career.
I've always been a nano-pleb when it came to shell-editors. Somehow I never grew fond of Vim or Emacs.
Linux - Even after switching to macOS for mobile development, I still can use most commands here
Git - While I had a short stint with CVS, I basically used Git my whole career
SSH - I don't know too much about it, but I stopped using FTP after I found out about SSH on my first job
JavaScript - I did C at high school, C++ and Java at university and VBA and PHP in my first jobs, but since I started JS 7 years ago I use it for everything
Photoshop - I never was much of a PS-pro, but my PS skills somehow have proven quite timeless and useful for over 10 years now, even when using GIMP
Reading code - sounds obvious, but after switching to JavaScript all libraries and frameworks I used where open source, so I could read the code instead of asking on StackOverflow
Asking people why - often I tend to simply write down feature requests and try to blindly implement them, asking people why they need them often reveals that they are requesting the wrong thing.
How I understood was that basics of OS (linux), source control (git), security (SSH), language (javascript), etc will have a lasting impact throughout one's career.
Did I understand it correctly?
Yes.
But the basics of Git are much different than the basics of CVS. (distribution)
Also, the basics of JavaScript are also much different from other languages (more dynamic than most, event loop)
Thank you for the clarification, K :)