You Should Write More As A Programmer #coding #programming #computerscience

preview_player
Показать описание
Doing THIS would have made me a better programmer. If I’d just written up projects I built, I could have accelerated my learning 10 times over. You know the feeling, you finish a project, then months later, you don’t really remember how you did anything. Document what you did in decent detail; it’s how you keep what you learned in your head for longer; I’m not saying write up and explain every single line of code, the syntax is never really the problem anyways, but focus on the troubles you ran into while building the project. Write down the problems you faced and how you solved them. Save this somewhere. You can look it up later, and you’ve just saved yourself a lot of time. Happy building.

Current Sub Count: 9,587

Music In This Video:
(I do get benefits from the above link)

WHO AM I?
Рекомендации по теме
Комментарии
Автор

That's actually a really good idea because the amount of time I run into an issue that I had a few months ago and I don't even remember in the slightest what I did

selenahammond
Автор

My empty Obsidian folder is ready to face the challenge

Silent_poet
Автор

Or build the system on a (idea) diagram and then start building around it, iterate it as do stuff. Reuse what works in other projects and if you are anything serious than a party trick programmer you will.. in 3, 4 years have your own framework that will put node or react to shame... Atleast for you and similar people like you.. how do you think so many frameworks sprout like mushrooms?

picklenickil
Автор

I made ML/ DL/ NLP notes on jupyter notebook... & i do revise it 🙏🙏🙏❤❤❤🙏

sidindian
Автор

Why i didnt see this video last year 😅

chams
Автор

I thought that too but I think the only thing you'll get is done wasted time. If you had a problem one/first time just fix it and keep moving. If it's the 10th time and you still forget how to fix it maybe read about the issue, but just writing notes on everything you did is not there way. Imagine you're writing a simple script and you think to yourself "oh I did it before, lemme go search though my notes." This will take forever, just google out or ask ChatGPT.

What you're describing does look like documentation and usually is just a few lines of comments above the function/class/struct. Maybe an example or two if it's module level documentation (module level basically means about the entire file, not one thing).

max_ishere
Автор

Is it okay if I go to college to get a cs degree without having any knowledge of coding?

nicolasaguirre
Автор

Yk ... Thats the point of infile documentation and readme ... Quite an amateur if not using either.

frostop
Автор

one of a good thing to do is make a simple website that will serve has a portfolio and or blog for all the future project. It will teach you the basics, and you can easily iterate on it too.

Ryuhikuro
Автор

Just save them on pc with some comments that's all

funnyguydragon
Автор

but I am writing scripts all the time.

luudest
Автор

Running into this working on a FiveM project, old scripts and solutions I didn’t document because I was in a rush back then and I’m having to go back to decipher year old code 😩 great tip! 👍

fcktom