My Productivity System as a Software Engineer ( Vim, VsCode, Planning, ... )

[@visionary_3_d]

I had a lot of fun making this video and I'm interested to see if you guys like this type of videos because I haven't made a similar one before. 🤠 LMK in the comments. I appreciate y'all.

[@mehmetakyuz5290]

Great video, specifically KZbin blockers you mentioned. I failed multiple times about Vim, seems like I gotta give it another chance. About "Don't Run Your Code"; I always thought it's opposite. Like test/run your code by each iteration, and go safer. Or like, gain confidence as you iterate and run it often. Otherwise, things can get blowed up. Yet, your method made me to re-evaluate this. I'm not sure this is a sign of capability of programmer as one way, because each of our brains work differently.

[@visionary_3_d]

Thanks for watching friend. I'd say you haven't failed with vim because it definitely can be difficult at first. I recommend trying it for a week without going back to ctrl and arrow keys. then if you want, after a week you can go back. I did that multiple times until I got good with vim. About "Don't Run Your Code"; I think it's a good experiment for everybody to try. If you're learning something new, then don't do this. Because you need to have a very good understanding of the code you're writing. Do the experiment when you're comfortable with the tools you're using and then and only then, this tip will save you time and make you more productive.

[@cpsthrume]

I already had the KZbin suggestions blocker installed, but then I saw the recommendations inside your video and I just had to search them. They are in my watch later playlist now, where they belong :)

[@anon3118]

I think vim is useful when you know exactly what you need to do, and exactly what features you need from a code editor.

[@visionary_3_d]

Well, in this video I was mainly talking about Vim Motions. Which is the set of keybindings vim has. Those are extremely useful and I don't just use vim motions for coding, but ANY kind of typing text. But... I agree with you that if you're gonna actually use Vim as an editor you need to experiment and spend a lot of time customizing your editor ( or just know what you want ).

[@mushroomthump]

This is great! KZbin is also my biggest social media distraction by FAR! I can keep the rest in check, but you're totally right about going to youtube to search for something you need then all of the sudden you end up 10 videos later forgetting why you came there in the first place lol. Although Im surprised you need so many plugins and theres not one single youtube browser plugin that does all of these things....

[@visionary_3_d]

Yep. The main extension is actually called UnHook. I use a few others too but that's the most important one.

[@averagetechnologyenojyer]

Loved your video, keep making more like these - u are an awesome developer ✌️😊

[@visionary_3_d]

Thanks!

[@extramanipulativemindseeke1065]

Super high quality content, Build your Empire my man ....

[@ayyappaj8111]

It's kind of funny that "I just got distracted while working and watching this video" :D

[@lerpmmo]

I'm kinda glad I got distracted and found your channel ngl.

[@visionary_3_d]

Haha yeah I’m also very happy about that 😂

[@amshenyesudas]

Expecting more videos on topic threejs and shaders, and other tech content, excellent presentation bro keep going

[@visionary_3_d]

Thanks man. I'm working on a tutorial next, no worries. 😀

[@Hudhaifa-1]

Great video from Great person ❤

[@vikasfx]

which linux distro do you use ?? ( just curious nvm )

[@visionary_3_d]

Ubuntu. (via WSL)

[@filixzs]

nice vid, just one thing, guys run your code! imagine writing 300 lines of code that does not work, from where you start debugging?

[@visionary_3_d]

Thanks. Yeah that has happened to me. The trick is you put break points in the code and follow the code step by step; making sure the values that you're getting are correct. That's called debugging. My point is that most people (including me), waste too much time sometimes by running the code and making sure every little thing works. By running the code at the end, you save time and you spend debugging time on the parts that need debugging. Also, my advice doesn't work if you're trying to learn something new. My advice is mostly for times that you're writing code that you're already familiar with. ( should've mentioned that in the video heh 😅 )

[@GEhehloopf]

@@visionary_3_d I agree to a certain extent that you don't need to run your code to make sure every little thing works; for instance, if you just add a logging statement, or change some print statement, you don't need to waste time re-running the code. However, I don't think it's a good habit to only run the code at the end of a feature/implementation. Even if you're familiar with a language, you are bound to make mistakes. You want to catch mistakes as soon as possible because it's much cheaper to deal with them early on.