Thanks for taking some time to respond. I would like to firstly say that at the end, I did say that these are just my opinion on how naming conventions should be.
In environments, yeah something can be abbreviated and well known, but I was referring to something where you are not working in a team (either solo or a public project).
You mentioned: "Two" is just arbitrary. Why not three? Or four? Or seventeen?
There is no problem with using many, but I find 2-3 works best for me and other developers I know, and this keeps the classes more manageable in my opinion.
You're welcome to name things however you want, in the end of the day: it's still your code; i'm just here to hopefully help others who haven't necessarily developed their own naming rules yet.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Thanks for taking some time to respond. I would like to firstly say that at the end, I did say that these are just my opinion on how naming conventions should be.
In environments, yeah something can be abbreviated and well known, but I was referring to something where you are not working in a team (either solo or a public project).
You mentioned: "Two" is just arbitrary. Why not three? Or four? Or seventeen?
There is no problem with using many, but I find 2-3 works best for me and other developers I know, and this keeps the classes more manageable in my opinion.
You're welcome to name things however you want, in the end of the day: it's still your code; i'm just here to hopefully help others who haven't necessarily developed their own naming rules yet.