Over these last few weeks now we've started to dive into more methods for "controlling" how we direct the code to accomplish certain tasks $-$ items like the if$/$else statement, logical operators, and other elements. These pieces make it much easier to direct our code based conditions $-$ like if a variable holds a certain value or some other condition is correct $($or not correct$).$ So now that we're looking closer into this lets explore the topic in our lives...

Your prompt this week is:

Previously we've discussed how software in our lives may have been gathering information from us and storing$/$using that information. Now lets drill down a little deeper and see if we can identify where that data is used to make decisions. Consider the if$/$else statement $-$ now that we know what it does $-$ think about $2$ different pieces of software you use $-$ identify a "workflow" in each that you envision where an if$/$else statement might be and describe it$.$ Make sure you identify what the "workflow" is$,$ and the decision being made $($both the $"$if$"$ and potentially "else"$).$

To clarify the expectations again here, this discussion doesn't need to be highly technical $-$ a plain English overview is fine. Just make sure you are being clear in your explanations $-$ there should be at least $2$ examples, each should be from a different piece of software you may use. Note that unless we have the source code, we can't really know for sure if there is an if$/$else statement there, but generally we can get a good feel based on what the software is doing. It's ok to assume one is in a location, even if we don't know.