Short version: 1. Flow and learn the good practice's and style guides. 2. Learn IDE shortcuts and install plugins according to your work flow (he hasn't mentioned even one plugin in this video). 3. See how others have done the thing and don't spend doing it from scratch. Nothing new here a lot of videos are already created like these, wasted my 12mins (9 in video and 3m writing this comment ) Hope saved a little for you 😉😉
I like that you mentioned learning your IDE. With all the arguments that arise about VS Code vs vim vs whatever else... the real point is how well you know how to use the IDE that you choose.
There's always vscode with vim bindings. And with all the plugins now for vim and neovim you can easilly run into a situation where you are just as bogged down in vim/neovim as you might be in vscode. The only thing i'll say is vim/neovim has a steeper learning curve that allows you to curtail these issues if you know what you are doing (lazy loading, fzf, ctags, etc.). But if you don't want to invest the time and just want to code vscode with vim bindings if you want is fine enough. Honestly the main reason to use vim imo is how seamless it is to interact with your terminal. Cause it is a terminal program. You can configure an IDE to do all the same things, start up servers, connect to databases, ssh, etc. But it just isn't as seamless and you don't have as granular of control obviously. Not to mention having a scripting language like bash or zsh to let you automate certain things. So really, if you aren't on a linux system or don't want to familiarize yourself with that, then there is even less reason to use vim/neovim.
@@bdinh3130 I don't disagree with any of that! It is a matter of preference, and you are exactly right, there isn't too much (that I can tell) that you can do in one that you can't do in the other. The point is to learn it! I think the trap people fall into (possibly part of your point) is that they think one is "better" or "easier" or whatever...but whichever you choose, you will be a more efficient programmer if you know all of the features. So, I guess the point is to use the one that you have the better time learning and even mastering.
Hey Forrest, firstly I would like to thank you for these videos. Secondly, I’d say I learned how important it is to have my code structured and organized in a manner that will allow for readability and reusability. I also now will look into what API is, and try to familiarize myself with the IDEs better.
I have recently moved to astro nvim, used vscodium, atom, spyder, codeblocks, kate in the past and only just finally realised that nowadays at least, at the end of the day, the main thing I care about, highlighting and suggestions, is all handled by the same lsps in the background regardless of what editor you use... Agreeable defaults (covers most of what you personally want), ease of configuration and modularity is all that matters really (but ceases to matter as much once you're familiar with something and already does all you need it to). For me, using multiple accounts on multiple machines, being able to synchronise those configs is also good. At this point I'm just a bit of a javascript/electron/json hater and like that my editor is no longer built on that, why do I need web stuff when all I'm trying to is edit some text? Nvim and its extensions also just feels way more transparent, but again, maybe I just prefer lua over javascript. I like to open and close my text editor frequently on different files, so its nice that it can do that snappily now. Also wasn't willing to put up with microshaft telemetry in vscode but vscodium doesn't package some default extensions like the intellij c extension because of the licence and the didn't have luck getting the other extensions to work (so you end up manually installing the original extension), it genuinely was easier to set in vim... Kinda annoyed that nvim has been around since 91, does everything I need it to and I've wasted so much time with shinier newfangled options that did less...
great video, I'm actually updating my dev Lifecycle and adding new habits along with removing some bad ones (like writing everything myself). Will try the techniques and will let you know
What I'm learning nowadays is that if the standards put in place on the codebase you're working on are shit, it's better no to use them. For example: create 3 files for 3 different components even if components B and C will only be used by component A and all of them are simples, simply because the standard is to have a file for each component. It makes analysing the component structure so much worse. Another one: using export default in a component file, to then import it in an index.js file in the same folder to create a module, as default and export it with another name. THIS. SUCKS. SO. FUCKING. BAD.
I was a bit underwhelmed at this video. Mostly advertising, not enough actual information. Really liked your early videos, though, and I hope you'll find your footing while balancing the content.
@textmforrestknight Thanks . I 'm not sure whats your primary skill, as I don't see any iOS related videos from your side recently. Is it even possible a person doing freelancing projects in both Web and iOS side-by-side ?
Short version:
1. Flow and learn the good practice's and style guides.
2. Learn IDE shortcuts and install plugins according to your work flow (he hasn't mentioned even one plugin in this video).
3. See how others have done the thing and don't spend doing it from scratch.
Nothing new here a lot of videos are already created like these, wasted my 12mins (9 in video and 3m writing this comment ) Hope saved a little for you 😉😉
you're the goat
Jeet
I like that you mentioned learning your IDE. With all the arguments that arise about VS Code vs vim vs whatever else... the real point is how well you know how to use the IDE that you choose.
There's always vscode with vim bindings. And with all the plugins now for vim and neovim you can easilly run into a situation where you are just as bogged down in vim/neovim as you might be in vscode.
The only thing i'll say is vim/neovim has a steeper learning curve that allows you to curtail these issues if you know what you are doing (lazy loading, fzf, ctags, etc.). But if you don't want to invest the time and just want to code vscode with vim bindings if you want is fine enough.
Honestly the main reason to use vim imo is how seamless it is to interact with your terminal. Cause it is a terminal program. You can configure an IDE to do all the same things, start up servers, connect to databases, ssh, etc. But it just isn't as seamless and you don't have as granular of control obviously. Not to mention having a scripting language like bash or zsh to let you automate certain things. So really, if you aren't on a linux system or don't want to familiarize yourself with that, then there is even less reason to use vim/neovim.
@@bdinh3130 I don't disagree with any of that! It is a matter of preference, and you are exactly right, there isn't too much (that I can tell) that you can do in one that you can't do in the other. The point is to learn it! I think the trap people fall into (possibly part of your point) is that they think one is "better" or "easier" or whatever...but whichever you choose, you will be a more efficient programmer if you know all of the features. So, I guess the point is to use the one that you have the better time learning and even mastering.
Hey Forrest, firstly I would like to thank you for these videos. Secondly, I’d say I learned how important it is to have my code structured and organized in a manner that will allow for readability and reusability. I also now will look into what API is, and try to familiarize myself with the IDEs better.
I have recently moved to astro nvim, used vscodium, atom, spyder, codeblocks, kate in the past and only just finally realised that nowadays at least, at the end of the day, the main thing I care about, highlighting and suggestions, is all handled by the same lsps in the background regardless of what editor you use... Agreeable defaults (covers most of what you personally want), ease of configuration and modularity is all that matters really (but ceases to matter as much once you're familiar with something and already does all you need it to). For me, using multiple accounts on multiple machines, being able to synchronise those configs is also good.
At this point I'm just a bit of a javascript/electron/json hater and like that my editor is no longer built on that, why do I need web stuff when all I'm trying to is edit some text? Nvim and its extensions also just feels way more transparent, but again, maybe I just prefer lua over javascript. I like to open and close my text editor frequently on different files, so its nice that it can do that snappily now. Also wasn't willing to put up with microshaft telemetry in vscode but vscodium doesn't package some default extensions like the intellij c extension because of the licence and the didn't have luck getting the other extensions to work (so you end up manually installing the original extension), it genuinely was easier to set in vim...
Kinda annoyed that nvim has been around since 91, does everything I need it to and I've wasted so much time with shinier newfangled options that did less...
More knowledge about tests is welcome. Best Łukasz
Yeah the refactor guru is a good site, haven’t used it in a while so thank you for the reminder
if you didn't watch this video on 2x speed you're doing it wrong
SAME! LOL
Attention rate go brrrrr
1.5x is already too much 😂
great video, I'm actually updating my dev Lifecycle and adding new habits along with removing some bad ones (like writing everything myself). Will try the techniques and will let you know
At the end of the day, the central role of the programer is managing complexity
We need a video for testing your apis!!!
Sounds logical
What keyboard is that?
I also want to know which keayboard is that you're using ^__^ looks pretty cool!
Hyped about the video on testing 🤟
What I'm learning nowadays is that if the standards put in place on the codebase you're working on are shit, it's better no to use them.
For example: create 3 files for 3 different components even if components B and C will only be used by component A and all of them are simples, simply because the standard is to have a file for each component. It makes analysing the component structure so much worse.
Another one: using export default in a component file, to then import it in an index.js file in the same folder to create a module, as default and export it with another name. THIS. SUCKS. SO. FUCKING. BAD.
thank you for his video ,it was relly helpful ,i have been wanting to learn about design patterns
Thanks
I only used simple linters.
Thank you Jesus 🙏
How to refactor code on a daily basis😮?
you look like that mormon dude from the series "Under the banner of heaven"
I'm sixth comment, and this changed my life
hey @ForrestKnight, I would like to see a video in which you do indeed go over API's. That can be very useful.
Why do we specify "std" namespace when header file iostream have definition of "cout" function?
thank you!
nice
Finally
does somebody know any plugin for refactoring help?
I was a bit underwhelmed at this video. Mostly advertising, not enough actual information. Really liked your early videos, though, and I hope you'll find your footing while balancing the content.
Refactoring
Familiar wt toolsIDE
API
why I can't be able to see you as a simple human?
Can you please share why you shifted from iOS to Web
@textmforrestknight Thanks . I 'm not sure whats your primary skill, as I don't see any iOS related videos from your side recently. Is it even possible a person doing freelancing projects in both Web and iOS side-by-side ?
@@prasannakumar-hh7cc that’s a scammer
I have a billion dollar idea we could sell to FB or Twitter but I need help coding it are you available for hire?
same
said everyone in sv ever...
Da coolest with with da billion dollar idea 😎
short version of this video is learn vim xD
xD true, i use neovim most of the time.
Ahh my like was, 999th 😅😆 i wish i could have been the 1000th!!
0:17 hmm efficiency and a vscode user hmmmmmmmmmmm 🤔🤔
it's possible to be efficient in vscode, but neovim efficient? nah
Hello boss plz help jop cook house kipping office boy iam very poor man my mom cancers pasnt Plz help
Sus
Hindustan mein rehna hoga, jai shri ram kehna hoga!
man I know this is irrelevent but you look like jesus. 😅
he IS the coding jesus tho
Another video scripted by Chat GPT haha, what's new in this???