First, ask yourself if you really want to invest time in learning Emacs. It probably isn't anywhere near the most important problem in your life, and won't change it much. In fact it might make things worse because it will make you aware of all the ways other editors are bad which didn't bother you before.
That might be problem as teams standardize on newer editors with good collaboration features, which don't exist or aren't as new-user friendly as in Emacs. Some languages also don't have as good integration with Emacs as they do with some IDEs.
That said, if you really want to learn Emacs, then
- go through the tutorial
- print out a good Emacs cheatsheet
- Have piece of paper or notebook to make your own supplement/complement to the cheatsheet
- use a Rosetta stone site if coming from Vim
- Force yourself to use the keybindings to move, not the arrow keys or the mouse. It will take a few weeks to get comfortable with the basic movement.
- Probably most important after the tutorial: learn all the help functions and their keybindings
- C-h ?
- info
- apropos
- where-is
- describe-key, describe-function, describe-mode, describe-variable, describe-bindings
- find-library
- understand how undo works
- package-list-packages to install packages
- Start a basic init.el:
- (fset 'yes-or-no-p 'y-or-n-p)
- (global-font-lock-mode t)
- (transient-mark-mode -1)
- Learn keyboard macros <--- Enormously useful
- After you are more comfortable, install and configure helm
- Read or browse the Emacs manual and the Elisp manual (in info)
- Read the "Mastering Emacs" posts for more advanced features
- Also Mike Zamansky's Youtube channel
That might be problem as teams standardize on newer editors with good collaboration features, which don't exist or aren't as new-user friendly as in Emacs. Some languages also don't have as good integration with Emacs as they do with some IDEs.
That said, if you really want to learn Emacs, then