There is self-documented code

In jobs whenever u write a code, u need to write comments in order for everyone to understand ( whoever is looking at Ur code)

In jobs whenever u write a code, u need to write comments in order for everyone to understand ( whoever is looking at Ur code)

code can do this as well

code can do this as well

In jobs whenever u write a code, u need to write comments in order for everyone to understand ( whoever is looking at Ur code)

def print_home_screen(): asdasdasddsa ... even non programmer will understand that

I doubt that yoi have written asm so far then

I doubt that yoi have written asm so far then

For people claiming you don't need comments, we should create a C/C++ Hobbyist group, for te ones that do understand why, create a C/C++ Pro group

😂 The AskMe group?

In jobs whenever u write a code, u need to write comments in order for everyone to understand ( whoever is looking at Ur code)

😂 The AskMe group?

It doesn't matter, when you're working with 100s of people, you need to make sure your code is as readable as possible

only the person who developed the code can understand code w/0 comments

it's easier to understand code when there are comments

only the person who developed the code can understand code w/0 comments

And often fucks up when needing to work on it later because he forgot half of it

guys, not all of us writing a good and readable code, better for u if another man will write comments for code

What isn't readable about that?

What isn't readable about that?

too much space for a simple func

here to those who say that comments are bad. wim, look away, dunt wanna cringe ya out 😝

too much space for a simple func

int add(int a, int b) { return a + b; } int main() { int x = 1; int y = 2; int z = add(x,y); std::cout << z << std::endl; }

Still, you're taking over a bit of my style 😉

yeah find only bad things

a big project will have more variables and it will get confusing

But don't flood with comments

good variable names, my friend. Use them

i can agree with you

it's because this code is short so u dont see it

good variable names, my friend. Use them

writing good codes, means beginning habits of writing good code. Write good variable names. int add is very straight forward rather than int doSomethingWithTheseVariables

Then again, they won't harm anyone so if it has use, don't wine about it

Just check the programming used for windows. It contains more 1000 k of lines of code, even if u have good variable name it's difficult to understand what's happening and leads to confusion🤷‍♂

Just check the programming used for windows. It contains more 1000 k of lines of code, even if u have good variable name it's difficult to understand what's happening and leads to confusion🤷‍♂

my point is comments are important

yes, but not always

Don't just copy paste, learn something;

This one doesn't even need a single comment to understand, but flooded with comments to make the copy paster understand what's going on

good for teaching

Right, but if you are doing something with a variable, does it really kill you to do something like std::vector<int> modifiedVector = modifyVector(modifiedVector); or is it better to do: std::vector<int> x = func2(x); Then have to comment what x and what func2 do?

Conclusion, Big and complex prg require comments Simple prg doesn't....

good for teaching

even if it takes 100 years and i come back to the code i'll understand what it means

U probably gonna die by that time🤣

PIE

Don't just copy paste, learn something;

So you would rather add: /* this function modifies a vector by rotating the elements positions by 1 */ void func2(std::vector<int> &x) rather than actually state what the function does? That is bad coding practice. Naming is key to writing good, readable, code.