@FreddyRangel85
I have noticed that most people that use either Vim or Emacs are usually pretty good programmers. But my theory on that isn't that it makes you better -- it's that the type person that takes the time to learn Vim or Emacs is also the type of person that takes the time to be good at programming as a whole. Kinda like parents who play classical music for their infant children -- it isn't that the music helps per se, it's that the kind of parents that do that will care about education in general.
@AlFasGD
I'm soon becoming 22, got hired as a dev at some company and there's this colleague that uses Neovim I think. Up until that point I would underestimate and laugh at the VI ecosystem, until I saw him in action. And that dude knows his stuff, it felt like magic watching him play with his keyboard, neglecting the presence of his mouse and doing common annoying tasks so unfathomably effortlessly and efficiently. I'm convinced, soon I'll start using those tools myself, and I can guarantee that in the future I'll be thanking myself for improvising on my tool usage, bringing me comfort in the passion I have.
@ifstatementifstatement2704
For 22 years I used basic notepad to program. Then one day I went to YouTube and saw programmers had fancy highlighted text.
@wmchristie
Mastering the editor makes it easier to get into and stay in the flow state when programming.
@headlights-go-up
I absolutely love that you can be a goof, crack jokes, enjoy some banter, yet still are able to switch on the 'dad tone' and impart some truly useful and valuable insight that you've gained throughout your career. Plus I think what you've shared here can be applied to a lot of other things. I.e. even though JS is certainly flawed and deserves the criticism it receives, I think if someone chooses to learn it, they should adopt the explorative mindset that you talk about here. Dive in, learn what you're using and why, pick things apart and be insatiably curious.
@dhillaz
Your point about "don't just do the job" resonates so much with me recently. I used to think everything was a distraction, but ever since I have stepped outside the box just even a little bit, by taking the time to investigate my tools, I have grown my confidence and productivity by an order of magnitude. I think as long as you are making deadlines and not blocking others, use your time to experiment and learn, it will pay you back real quick.
@miguelguthridge
I've spent a few years really learning VS Code, and after 2 years worth of customisations and refinements, I'm pretty damn quick at it. I completely agree that the editor you choose doesn't matter - as long as you take the time to get good at it. It's kinda disappointing how many people I see who don't take the time to change their editor to work in a way that makes sense to them.
@scottiedoesno
Watching you use Vim a little over 2 years ago was what convinced me to live like this. Thank you for starting my programming career off with a bang!
@patrickprucha5522
Im 60 years old and still learning. You make a very very good point to the future generations. You are 1000% right. You have to learn the tool to master it. And you wont master in 10 minutes. Its a continuous process. Keep up the excellent work!!!!
@nikfp
I'm about 3 months in on Neovim and I've learned a number of valuable things since I got started. 1) Sometimes you don't know what you don't know. By setting up Nvim from scratch and adding features as I saw a need, I realized how much VSC has built in, and how much of it I wasn't using. I considered myself decent at using VSC, but now I know I could have gone farther. 2) It's useful to explore different ways of doing things. By learning the modal editing philosophy in Vim and learning how to compose motions together, I realized that I can have a more organic conversation with the editor through the motions than I ever thought possible. VSC in contrast has a model of creating shortcuts tied to combinations of keys, and it took a lot more mental overhead to remember those shortcuts. 3) Whatever tool you use, embrace how it's different. I made the mistake of trying to turn Nvim into VSC and wasn't happy, but when started over from scratch I ended up with something I really, really enjoy using. The key difference was in letting go of some of the things I thought I needed. Most notably, I can find anything I want with the Telescope plugin, and I swapped out the fuzzy find algorithm to fzf-native and it's super fast and fluid and fits the way I want to search. Because of this, I have not needed a file explorer plugin, and the built in Netrw is more than enough for the infrequent need to traverse the file tree visually. All in all, I'm not going back to VSC for daily use, but I'll keep it around for the odd occasion that it has something within reach that I need.
@keithprice1950
The problem with this (even though I totally agree) is that there is just an overwhelming amount of other stuff to learn to even get your foot in the door as a developer. If you are learning web development or new to web development you're already juggling the massive amount of stuff you need to learn just to build simple apps, then throw git/git hub in there also, learning the command line etc. On top of that then learning an editor inside out is just a hassle (at least at the beginning).
@samgould8567
At the other end of the spectrum, you can end up fiddling with your tools more than actually using them. At some point with vim and tmux, I stopped fiddling except where there was a clear and immediate benefit, but with Emacs it just never stops. That may speak more to my own problems than with the tool itself, or maybe it just goes to show how malleable and awesome Emacs is.
@goktugerol1127
Once Linus Torvalds said: Talk is cheap show me the code. Who cares what editor you use, just deliver a good work.
@dentjoener
Preach! As a full time Java dev (come at me), I use IntelliJ all day every day. And let me say, every time I have to use another tool by another company or free or whatever, I feel like going back to the stone age. I've been using this for almost 10 years now, and there's no way I will go back to anything else. I love vim as much as the next guy, but to me, the IDE can do anything I need it to do. Code, refactor, git, databases, docker, debugging etc etc. Yes it's $600 a year, but as a contractor, I make this back in a week at most when I use it.
@780Chris
I was a VS C*de user until this March, I watched your vim videos and started picking up NeoVim. It’s just so fun customizing everything to my liking and learning/remembering bindings that will make me faster.
@TheRiquelmeONE
i remember when i had almost no idea about git and just mindlessly used a tool i did not understand at all. As soon as anything went wrong i was just helpless. I'm so happy that i followed the advice of a coworker who told me to learn how to use git in the console and focus on that even if it is confusing at first. That helped me a lot and now i can use various tools for git and things magically just work now. And in the worst case i can always fix things in the console. Same thing for anything involving linux.
@nandans2506
Whatever tools you use it's incredible seeing people who have mastered their tools. Who are so quick it feels like we are solving problem as we are thinking. Tool isn't coming in between. It's not just about editors. Bash prowess, os prowess, ability to spin up quick servers, prowess with whatever apms, log aggregators, analytics tool they use, db queries etc. Many of us never go deep enough, we'll just figure out something and then think we'll check it out when we have to
@JeffryGonzalezHt
About 1/2 way through my development career I quit and went to film school. I gravitated towards editing, because computers. I had a teacher that said "You are never done with an edit. You are always up against a deadline. The difference between a good edit and a bad one is how many things you can try. Learn your tools so you can try a bunch of things". He made us use our editor with no mouse by the second class. I feel the same is true in coding. I'm not that good. I can just try a ton of stupid things to get to the more "right" thing in the same amount of time as other people still on their first dumb idea.
@PeterSteele111
2 years into my current job and I have found myself slumping back into this mentality of just get the job done and clock out. Watching your vids has definitely sparked up the love I have for the tools and the setup to play around again though. Funny I came across this video when I did because I have been trying to daily drive neovim and getting frustrated with it (I have primarily been using VS Code and PHPStorm), but I am getting better at it. This kinda puts in back into perspective to keep at it. Though I am now into my early to mid 30's at this point, so i don't quite get the luxury of discovering this in my early 20's, but it will have to do. I have been coding since 2004, but back then it was all about making the cool thing or showing off in high school, not so much about learning the tools. One day maybe Ill be able to look back in another 10 years and say hey, youve come a long way. Thanks again for the content, it definitely hits home for me :)
@ThePrimeagen