Answer:
c.
Explanation:
I believe that in this scenario, the best option for this data would be a hash table using open addressing with 1,800 entries. Hash tables consume more memory than lists but it makes up for it with much faster response time speeds. This is because hash tables work on a key:value system therefore, the license plate can easily be grabbed from the database extremely quickly by just plugging in the plate number. Doing so will retrieve all of the saved information from that license plate. That is why hash tables have a constant time complexity of O(1)
Answer:
Steps 2 and 3 needs to be switched.
Explanation:
e2020
Answer:
Following are the program in Python langauge
person_name = input() # Read the person name by the user
person_age=0 #declared a vaiable person_age
person_age = int(input()) # read person_age by the user
person_age=person_age+5 # add 5 to person_age
print('In 5 years',person_name,'will be',person_age) # display the output
Output:
Amy
4
In 5 years Amy will be 9
Explanation :
Following is the description of code:
- Read the value of the "person_name" variable by the user by using the input function.
- Declared a variable person_age and initialized 0 with them.
- Read the value of "person_age" variable by user by using input function and convert into int by using int function
- Add 5 to "person_age" variable and store again them into the "person_age" variable.
- Finally, display the output which is mention in the question.
a. stateTaxRate - A good variable name because it represents what it holds, the state sales tax rate, without being too wordy. Also correctly capitalized in camelcase.
b. txRt - A bad variable name because while short and simple, it is too hard to understand what the variable represents.
c. t - A very bad variable name if you plan on using the variable often. Far too short and you will forget what it represents and is needed for.
d. stateSalesTaxRateValue - A bad variable name because it is just too wordy. Cutting it down to A's variable name is much more reasonable
e. state tax rate - A bad variable name and probably invalid because it has spaces in the name.
f. taxRate - A good variable name if there are no other tax calculations other than state tax rate. Otherwise you would confuse state vs local tax rate or something, making it a bad variable name.
g. 1TaxRate - A bad variable name because the number 1 has no reason being in the variable name. It doesn't add anything to the name.
h. moneyCharged - A bad variable name because it is not specific enough in explaining why the money is being charged and what for.