For the javelin throw event, you will soar as you write a time logger.
(Imagine Billy Mays reading the next sentence.) Soar to new heights as you suddenly impress your boss, your colleagues, or your friends with detailed logs that tell them exactly where your time goes during the day. All people in IT or consulting eventually are required to provide status reports or activity logs either to prove where time was spent on a project, or to justify the amount of time spent on a seemingly trivial task. Or maybe it is a positive procedure that provides documentation to justify increased head count. Whatever the reason, the outcome is the same: log it and document it, or else it does not exist. Before you reach for a pencil and a piece of paper, pick up your favorite script editor and scripting language and toss the javelin into the air. This one will land exactly you-know-where after you complete this scenario.
In this scenario, you will write a time logger. The essential characteristic of a time logger is time-stamped text entries that describe a particular activity. You must provide the means of writing time-stamped text entries into a text file or other storage mechanism to complete this task.
Note: Like many of the other entries that make up the Summer Scripting games, this event can be easily expanded upon to incorporate additional features for the time logger. You must decide how you want to receive the input for the entry. You must also decide if you to use a timer mechanism to provide summary information such as the activity took two hours. You may even decide to allow categories of activities such as troubleshooting, setup, help desk calls, answering e-email, or project planning. How you choose to answer this one and the features you decide to incorporate will determine your peer review at the end of the games. More importantly, it will determine the usefulness of your time logger.