Message from C, C++ talks

May 2019

β€” Even if it takes 100 years and i come back to the code i'll understand what it means

β€” PIE

β€” U probably gonna die by that time🀣

β€” Apple pie or ?

β€” 

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.

β€” I undersatnd this already

β€” I'll do both

β€” I would rather write:

void rotateVecBy1(std::vector<int> &toRotate)

β€” Imagine working at a company like google

β€” Ok, guys, lets make conclusion:
Who prefer to comment ur code - do it
Who prefer not to do it - don't do it

Message permanent page

β€” U would need to comment it

β€” Comment as necessary

β€” You guys forget that if you comment what a routine does and it fucks up, someone else can figure whats going wrong seeing the wrong code and the comment of what its supposed to do

Message permanent page

β€” There you must comment your code

β€” No, sonic.