This course is designed to engage you in practicing what you have already learned, and also in growing your knowledge with new programming concepts. You acquire the skills it takes to rise to programming challenges. Data and analysis are just a few aspects of said challenges. As previously defined, “Design Thinking” is the design of things, products, services, and problem solving, as well as the thinking behind the design of things, products, services, and problem solving. Data gathering, analysis application, and forming a conclusion(s) from the data are all essential in Design Thinking–an objective of this session. An integral aspect of Design Thinking is the gathering of data, how it is assembled, and design from the data through firsthand consumer observation. Consumer observation is the practice and process of going out into the world to observe side-by-side, one-on-one, moment-by-moment, actual routine (to an extent unconscious) experience(s) and daily practices of a consumer, in order to discover needs and wants that may ultimately result in products, services, or problem solving. For example, consumer observation could involve observing commuters, skateboarders, nurses, or someone navigating through a computer program or software, as they improvise through their daily lives or professions. From the reading in Design Thinking on consumer observation, how could data gathering through consumer observation be beneficial in programming? What are some of the potential advantages and disadvantages of data gathering through consumer observation in programming? How does the process of data gathering and customer observation help in creating Python programs that meet the needs of the end users? Having read through the case study, include any concepts that relate to Design Thinking which you observed in the case study.