which of the following is valid advice for naming variables?\n a. to save typing, make most variable names…

which of the following is valid advice for naming variables?\n a. to save typing, make most variable names one or two letters.\n b. to avoid conflict with names that others are using, use unusual or unpronounceable names.\n c. to make names easier to read, separate long names by using underscores or capitalization for each new word.\n d. to maintain your independence, shun the conventions of your organization.

which of the following is valid advice for naming variables?\n a. to save typing, make most variable names one or two letters.\n b. to avoid conflict with names that others are using, use unusual or unpronounceable names.\n c. to make names easier to read, separate long names by using underscores or capitalization for each new word.\n d. to maintain your independence, shun the conventions of your organization.

Answer

Answer:

C. To make names easier to read, separate long names by using underscores or capitalization for each new word.

Brief Explanations:

Using underscores or capitalization (e.g., camel - case or snake - case) for multi - word variable names improves readability. Option a makes code hard to understand, option b with unusual names is counter - productive for code readability, and option d goes against good practice of following organizational coding conventions.