Blog 2

Estimation and calculation are almost two contradictory items, on one hand you have an exact measurement, and in the other you have something that is just an estimated guess. When dealing with things where the margins don’t need to be exact, estimations can be an acceptable option. But when things need to become specific, calculations will always be a necessity. This ties greatly into assumptions and data, pretty much the same concept, just worded a little differently and for slightly different purposes. In today’s digital world where we may be in need of directions, we are going to rely on data to get us where we need to be when using maps. Take google maps for example, the users rely on data from google maps to get their directions and google keeps these maps updated with data, whether it’s from other map users, construction companies, or just general employees doing their jobs to make sure the user gets the best possible rout. Take construction on roadways for example, google must rely on data to stay up to date on those kinds of things because if the maps always assume that a certain roadway will always be open, it will prove to be troublesome to the user following the map to a closed road when it could have been avoided with an alternate route that would have easily led to the same destination. But assumptions are a good thing as well, when estimating things out, assumptions are always the biggest players in helping estimates because those generally tend to be the things that can be easily relied upon. If calculation the time it takes to take a quick trip across town to go the movie theater, it’s always good to take on the assumptions first because those will be your biggest factors in this kind of traveling.  You’ll  need to make assumptions based off of what time of day it is to best deal with the Chico traffic to get the movies on time.