4. Only take notes of those concepts which you use very often and find it difficult to remember them. Yeah thats everything lol

Thats what commenting is?

thank you too

​@@Turnpost2552😮

thank you mate

Do game devs need to learn design patterns? I feel like following SOLID and clear-cut design patterns would make for good code that is already self documenting, but maybe comments would still need to exist. I haven't learned design patterns yet as right now I'm learning multithreading, and I heard design patterns should be one of the last things an entry developer should learn, as it can get pretty complex. Would you agree that learning design patterns is not easy - that some can become complex? Or should I learn it immediately - asap...?

Really! This is very bad, commenting should be the last resort. But I do agree with the documentation.

"All code is at its core is a communication tool" completely agree and which is why comments should only be for things you cannot capture through code, i.e., why something is implemented in a certain way vs "how" its implemented.

Focus on Very clear variable names, this isn't the 1980's and you are not character limited. m_Debug_Iterator is not a variable name it's gibberish or obfuscation, variables should either be adjectives, verbs or objects (language sense). Then use xml summaries etc to document your methods. Only comment choices you can't explain with your code inline, everything your can't fit in that like program logic, document it. I was very lucky to have a talented and pedantic lead programmer actually teach me things especially regarding making code understandable, still learning but it has been invaluable experience.

In school comments were just as important as the code you would loose so many marks if you didn't comment.

The same could be said about any skill worth learning. You could take all the notes you want on it... But it doesn't really help you out if you don't actively practice the skill.

This is it what he said what so ever

@@Othorius I always found memorizing details to be much harder than understanding concepts Maybe it depends on the person? Memorizing formulas might be your weakest link, for example.

Nope wrong. Situations variable constants making certain shape if all elements in place making certain way then apply this

If you learn one thing try it simple way different ways then shortest way for different scenarios then find common ground, revise that puzzling step and it's solution

@Ryan Tandy No advice is "final". If you think that you need to use comments in your project, DO IT. Comments will always have a place in our code, some things can only be explained by comments and if it makes the team happy, even better.

Do you mean coding according to whatever style guide is used on the project?

@@krillansavillan Yes and no. Sry for the riddle, but life is always about balance and change. If you have a good company you'll have style guides and standards per company then per project, but it's ok if you have only standards per project. Who decides the standards? "The TEAM" - All the people involved in the project. The interesting thing is that standards can change and should change with time, because the team changes (people come and go) and also because the people in the team get better with years of experience. (programming as a practice also) So yes, code to the project standards, but don't be afraid to change the standards for the better when you guys feel like they need a change.

@@TricoliciSerghei thanks Serghei, I appreciate the response. Totally get it how it's not just black or white.

@@krillansavillan Glad to be of help. Cheers!

Totally agree.

May you share with me document ? Plz

same for me,, some people need it, as it helps you stay organized, and worry free, cause you've got everything written down, your own personal stack overflow.

That's exactly why I started writing comments. At first I didn't do it and it happened to me that I would forgot how part of my own code works. Since then I started writing comments, even though I should be writing more comments according to this guy, since I am still a beginner.

Even before watching this video my preffered option was to comment the code than to take notes but I still do take notes of some things, how some things work.

Thankyou

thanks bruh, you saved me 10 mins.

You're a legend 🙏

I don't really understand what you mean by the 2nd one, mind explaining more to me? 😶

@@emmancrafts. I'm still relatively new to building my own apps but the best examples can be found on github. To put it simply, whenever you look up or download someone else's work, there are usually readme files that come attached with it. This is documentation. Say you were building your first app, like a food suggestion app. Your documentation would be the readme file attached to the app, explaining exactly what the app does and what its purpose is. To be even more thorough you could also explain what skills you were trying to polish by building this app. As you build your skills, your documentation should also become clearer and more intuitive.

How's it going now?

You should take notes on things that don't come up often, but things like loops, vars, functions, etc should all be learnt by muscle memory. That isn't the stuff you should have to google.

same here. Take my advise, never copy a full code from your source. Let your hands get used to typing codes, it worked for me.

Wait until you get back to your notes in the future and you don't understand sh*t about what you wrote no matter how well you wrote it.

How's it going now??

That's fine if the company keeps all of its history of specs because sometimes you have a sleeping bug that can pop up 10 to 15 years later and you see what the code does, but it doesn't say anywhere what the business rules intended it to do. Sometimes, the person who worked on it originally doesn't remember doing it. If the full history of specs isn't kept, the comments are the next best thing.

Gonna have to disagree-ish; in an enterprise level code base, part of good coding practices along with readable naming conventions is updating the comments and aptly naming commits.

Have worked on large scale enterprise systems. Well named functions/variables/etc. is the baseline. Good comments are paramount to maintaining a large codebase. Code often cannot read as prose nor explain intent. The GREAT habit is updating any surrounding comments when you touch the nearby code

I've worked on systems where the people who had designed it were self taught. The problem was it showed in the code. The designers clearly didn't know the difference between a goto and a gosub, the applications would behave in ways not intended because they didn't understand the memory stacks. I've seen over-use of small variable names as if the computers used still had 2k of memory and there was very little in use of comments which would describe what the code was supposed to do. I've seen over two pages of code in some programs that was no longer reachable by the code that ran but it wasn't commented out so a person could waste time reading non-accessible code etc. This bad coding could have been prevented by having the programmer reading a few books on good coding practice.

​@@HepCatJack I can agree to some extent, however I am 100% self taught where my field of study is within C/C++ and I dove into 3D Graphics Engine Design, Hardware Emulation, and more. I taught myself all about the entire process. Not just on the software side of things, also at the assembly level, the compiler and linker or interpreter side of things, I learned how to use the debuggers. And it doesn't stop there. I even dove into and researched into OS design, as well as ISA or Computer Architect Design. I mean building a basic CPU from Logic Gates! There's a lot more than just the stack frame and stack pointer involved. You have calling conventions, name mangling - symbol tables, virtual function tables, utilizing the cache, understanding the branch predictors especially with modern systems that implement out of order instructions, and more... and the list goes on! If it involves a Circuit and Software, I'm game about learning how it works and how to instruct it to get it what I want it to do! I even started to pick up a little bit of Python and some JavaScript when I started to learn about A.I. Algorithms, Neural Networks and Machine Learning. It's not just the programming, nor the data structures, the algorithms, Big O, etc. it's also all of the math that is involved from basic Algebra to Linear Algebra and Vector Calculus, Boolean Algebra, Lambda Calculus and even Number and Information Theory! I have had some college courses in the mid 2000's around 2005-08... but none of my courses involved computer science... the highest mathematics I had was Calc II and Physics II. All of the rest was all self taught! I believe the comment you made can be self evident in many cases sure, but I also find it to be very stereotypical. In all honesty, it comes down to the individual and how they apply themselves! Some of your best engineers or programmers don't have any "formal education". They are smart enough to figure it out on their own. I would tend to think that the stuff you are seeing may not necessarily be from someone who's self taught. It could actually come from someone with a bachelor's degree, one who took it and just barely passed with a high C average about a 2.8-3.2 compared to those with a 3.8-4.0 GPA... I'm not claiming this is so in your particular case, I'm just stating that it is highly possible, even highly probable! They could have either just happened to do well in the interview or got lucky as opposed to someone who knows the entire workings of a computer system as well as the different layers of abstractions, the different paradigms, idioms, etc... One should never assume something based on a stereotypical mindset without having more information, more details and proper context! Just because there's one bad or poor apple doesn't mean the entire orchard is bad! Why do I say this? Throughout the years, most of your inventions came through Garages! And many of those people didn't even graduate from high school! It's almost analogous to the old saying, "never judge a book by its cover!" From my own experience, reading books can be good and helpful and do make a good reference, however, one of the best ways of learning is just by doing it through trial and error, finding what works and what doesn't, finding your mistakes and fixing them. A good programmer, software developer, computer scientist, software engineer, etc... isn't based just on their ability to "write source code". No! What makes them good is their ability to Debug It! The most tedious and dreadful aspect throughout the entire development cycle! If you can debug it! Then you know what's going on under the hood!

Thank you very much!

Back in the day? Huh

I'm stuck at high school programming teacher ....some people are very lucky😂

Keep it up and do what works for you. Definitely can't go wrong when you start building good habits early in your learning!

This is a great tip! Like coding flash cards, love this idea and makes it a lot easier for note takers like myself to have a quick reference in your own words.

Simply when you're starting at coding as a beginner u need some notes...but once speed up and running you might not need them...go with comments and documentation...

hahaha 🤯

I feel like this mostly only works when you're solving algorithmic problems. If you're writing some layout code, or some simple stuff, it may be overkill

@@chizonwazuo Yes, since most problem sets there are related to algorithms.

Thanks, will do!

Not anymore after this video lol 😂 thanks! I’m on js now

Yep, something like that. I 'm doing the FCC so I download each answear and comment it. So when I'am building and dont know how to, just search the file and read my comments. Also each line of code from FCC I rewrite it in VSCode for practicing.

I need mentor for my coding journey I learn c then data structure now I m learning greedy algorithm I know c++,html , css little bit too but after completing dsa should I go with java or c++ ? help me out buddy

Yes, I’m so used to learning this way especially coming from a science background. Your advice makes great sense! Thank you!

HEY DORIAN! I've been in this channel since you have a small subs. Can I ask do you post you videos outside like FACEBOOK to increase your views or KZfaq just got you through Algorithm? sorry for the non related question :)

Thanks! Really trying to step it up and learn how to use this new camera!

Hey might giving an example of this ? Like an example of one drawing you did with all this info. Your strategy seems really interesting and a good approach to understand

@@djamz3793 Imagine a stack. It is a container with a pointer variable called top with value -1 and a variable capacity, which tells you how many items you can put on the stack. Open inkscape or other program for vector graphics drawing and draw a box with open top, call it container, then draw a red horizontal arrow right at the bottom of the box, to the right of it write top and set the value of this variable to -1. At the of the box draw another red arrow and at the top of it write capacity and set it to how many items your stack can have. I use orange color to describe all the parts of my data structure that normally would be considered variables. So box, top and capacity would all be orange. Next to your stack draw some blue boxes and label each of them item. These are items you will be putting on your stack. Once you have your basic structure you are ready to draw how actions will affect your data structure. Lets say you want action called push, which is normally used to put an item on a stack. Copy your basic data structure and paste it below. Label it push(), Draw a black arrow from one of items to point into the box. Then draw a green vertical arrow under the red horizontal arrow next to variable top. It shows that value of top changes from -1 to 0 as you push an item on the stack. This is a very simple example of how you might visualize things. You should do similar drawings for other operations defined on the stack like isEmpty or pop. It does not really matter how you draw. What matters is, you should use colors, make all the variables available for change on your data structure and be precise how they change as you manipulate your data structure. Sometimes it takes several copies of the basic data structure to depict what happens as you sort or do some other thing. You might say, this is too time consuming method. It might look like that, but remember that you do it once. Once you have these drawings, your code based on it and tests you are set for many many years. When you need a quick reminder how things work, you take a quick glance what you drew and you know immediately. Your code should be based on your drawings, and your tests on your code. This is nothing different to what you would do while solving a maths problem. Drawing gives a nice face to programming and helps to define classes and actions on them very cleanly. On top it is an extremely pleasant part of coding process. Finally, you are left with something that you can always come back to for a quick review. Finally, once you have drawn a couple of things, you have reusable components, like arrows, items, containers, you can use to draw other things quickly. Once you have started with this it becomes a habit, one which is invaluable when you have to deal with a complex data structure with many moving parts ... in fact, when you see that there are too many moving parts, it is time to separate some parts and move them to a different drawing. Your drawings should have no more than 6 moving parts as your classes should not have more than 6 variables in them. Hope this helps.

Definitely feels more comfortable! I will be trying to make all my new videos better and better! Thanks for watching!

@@DorianDevelops Pleasure mate

Great advice, thanks.

You should take notes. The point of doing a course is not to get through it as quickly as possible. It is to learn as much as possible. And no taking notes does not take your focus off what you are learning. It actually helps you.

@@JustinDAMusic Did you watch the video entirely ?

It's something I think that we all do when we're first learning. I'm old and much of my early notes were pen and paper 😂 that was messy as well. Had to step up the production values to try to reach a wider audience. People really like "entertaining" video.