Some system analysts argue, "Give users what they ask for. If they want lots of reports and data, then that is what you should provide. Otherwise, the users will feel that you are trying to tell them how to do their jobs." Still another group of analysts argue, "Systems analysts should let the users know what information can be obtained from the system. If you let the users dictate, then you will never get anywhere and/or go down costly paths because the end-users really don't know what they want and do not have the technical knowledge or understanding of code, data-basing, and systems." What do you think of these arguments?

Write a program that keeps asking the user for new values to be added to a list until the user enters 'exit' ('exit' should not be added to the list). these values entered by the user are added to a list we call 'initial_list'. then write a function that takes this initial_list as input and returns another list with 3 copies of every value in the initial_list. finally, inside print out all of the values in the new list. for example: input: enter value to be added to list: a enter value to be added to list: b enter value to be added to list: c enter value to be added to list: exit output: a b c a b c a b c note how 'exit' is not added to the list. also, your program needs to be able to handle any variation of 'exit' such as 'exit', 'exit' etc. and treat them all as 'exit'.