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

Рет қаралды 2,117

Күн бұрын

These are some of the tricks I use to become productive as a programmer. ✌
Ultimately the most important thing for a developer is to write good software that works.
With these 3 steps I can save time for things that I love ( creating stuff ) and intentionally use that time to invent and create new things.
1. All the blockers I use:
github.com/visionary-3d/no-di...
2. Learn Vim with my favorite youtuber/streamer:
• Vim As Your Editor - I...
3. Automated plan file generation:
github.com/visionary-3d/plan-...
My VsCode Config ( themes, vim, etc... ):
github.com/visionary-3d/vscod...
References that inspired me to make this video:
Hamza Ahmed:
• This will literally ch...
Ali Abdaal:
• How to Build Your Ulti...
The Primeagen:
/ @theprimeagen
Support this channel 💖
My ETH Wallet:
0x61621F0cE4665789863569C6211af4Ea7e08FC82
Chapters:
00:00 - Intro
00:17 - Definition Of Productivity
00:25 - Step 1
00:40 - Example Scenario
03:13 - Solution
05:12 - Doing The Right Things
05:35 - Coding Environment
06:20 - Vim Motions
08:48 - Don't Run Your Code
10:51 - Automation
13:33 - Outro
--------------------
Visionary 3D:
Follow me:
x.com/visionary_3_d
Discord Community:
/ discord
Shaders Crash Course:
• Three.js Shaders (GLSL...
My Shaders Playlist:
• Shaders
My VsCode Config:
github.com/visionary-3d/vscod...
Three.js Boilerplate:
github.com/visionary-3d/three...
#threejs
#3d
#3danimation
#glsl

Пікірлер: 22

@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 KZfaq 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.

@extramanipulativemindseeke1065 Жыл бұрын

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

@anon3118 8 ай бұрын

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 8 ай бұрын

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 ).

@cpsthrume 7 ай бұрын

I already had the KZfaq 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 :)

@thisisavinash Жыл бұрын

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

@visionary_3_d Жыл бұрын

Thanks!

@mushroomthump Жыл бұрын

This is great! KZfaq 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.

@Hudhaifa-1 Жыл бұрын

Great video from Great person ❤

@ayyappaj8111 9 ай бұрын

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

@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. 😀

@lerpmmo 7 ай бұрын

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

@visionary_3_d 7 ай бұрын

Haha yeah I’m also very happy about that 😂

@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.