this. I hate it when people let you want to remember all class fields and methods and conflicting local variable's names. UGH. USE this, super, and "qualify" static stuff in this exact manner as well. Thank you.
This part is too personal and specific. Nobody needs to agree...:
m_ and p_ are good naming conventions since they show only scope, but if you'd [use them with camelCase instead of PascalCase at least in Java, and] make sure you're using these only for scope, I'd be happy.
this. I hate it when people let you want to remember all class fields and methods and conflicting local variable's names. UGH. USE this, super, and "qualify" static stuff in this exact manner as well. Thank you.
Place I am at now doesn't allow to use this. for self calls and when I first started here (about 5 years ago) it was a huge adjustment to not use them because for the first 16 yrs of my career I was at a place that required it.
I still miss it because I think it improves readability, it makes method calls consistent and let's me know exactly where the method is when I am reading the code.
2
u/Brahvim Apr 14 '23 edited Apr 15 '23
this. I hate it when people let you want to remember all class fields and methods and conflicting local variable's names. UGH. USEthis,super, and "qualify"staticstuff in this exact manner as well. Thank you.This part is too personal and specific. Nobody needs to agree...:
m_andp_are good naming conventions since they show only scope, but if you'd [use them withcamelCaseinstead ofPascalCaseat least in Java, and] make sure you're using these only for scope, I'd be happy.