Should each commit in a branch implementing a new feature be prefixed by “feat:” using conventional commits?
Consider I’m working on a branch feat-1 implementing a new feature.
Where does the practice of naming variables with the prefix “my” come from?
I recognize that there are situations in which “my” is semantically useful, but I have met multiple professional programmers that have a habit of using this everywhere that it’s not – “my_var”, “myTemp”, etc. I recently discovered that my friend’s professor is using this in his assignments, which made me wonder if there is actually some historical reason for this.
Using a function’s return value as an if condition, good practice?
Do you think it is a good practice to use function return values as if conditions? I’m coding in PHP atm but it holds for many other languages.
Using a function’s return value as an if condition, good practice?
Do you think it is a good practice to use function return values as if conditions? I’m coding in PHP atm but it holds for many other languages.
Using a function’s return value as an if condition, good practice?
Do you think it is a good practice to use function return values as if conditions? I’m coding in PHP atm but it holds for many other languages.
Why is the following naming guideline different between OO and non-OO languages?
I am working with a non-OO language and I’m trying to name my routines consistently. I came acrross the following guideline from Steve McConnell’s Code Complete:
What is ServletUtilities?
The answer in this question suggests creating a ServletUtilities class to handle text conversion between Java strings and XML text.
What is ServletUtilities?
The answer in this question suggests creating a ServletUtilities class to handle text conversion between Java strings and XML text.
Naming convention of getters and setters [closed]
Closed 10 years ago.
Naming convention of getters and setters [closed]
Closed 10 years ago.