Machine Problem 2 = Doom

(Click to Enlarge)*

I thought I was a procrastinator. It turns out that my computer science professor has written the book on procrastination. To understand the whole situation, we must trace the timeline back about a week ago:

Early in the week we were introduced to our new machine problem. Typically, the introduction explains enough of the basic gist of a problem to allow us to work on the design of the problem. In other words, Dr. Geisler said something to the effect of, "Your new machine problem will be a simulation of a trucking company and you will track some statistics about the inventory." After drawing a few diagrams, pointing out some of the details of the problem, and allowing us to ask questions, he assured us that he would make the specifications of the problem available to us online soon. He also mentioned that it was possible for some of the details of the problem to change, but the written specifications would be final.

Thursday rolled around and we turned in our design for the problem. Friday rolled around and we still did not have the specifications of the machine problem yet, so we brought it up in class. Dr. Geisler explained that he was busy with the Programming Contest, but during the contest he would sit down and work on it. The weekend passed, and Tuesday rolled around. At precisely 12:18 PM, we were given the problem specs in finalized form. Jay and I thought it prudent to sit down and read through them. While we read, we came up with list of questions that we needed to ask in class the next day. One of the questions was that we couldn't seem to make our numbers match his and we needed to know if we were in error. At this point, we had not began the programming and fully expected Dr. Geisler to postpone the due date at least a day or two.

Wednesday, 2:05 PM: "Dr. Geisler, when will the machine problem be due?" I queried. Dr. Geisler responded, "We talked about the specifications in class a week ago so I hadn't planned on moving back the due date." That was an instant jaw dropper. I was absolutely petrified, furious, and shocked. Masking my dismay, I continued to work through our list of questions. I asked about his math on the example input and output. Guess what? It turned out to be incorrect.

Let me spell out exactly what was running through my mind: "We just got the specifications 26 hours ago, your example is incorrect, there are other typos in the sheet, and the Machine Problem is due in 20 hours. Ahhhhhhhhhhhhhhhhhhhhhh!" This was the ultimate insanity. I immediately knew that all my sleep was doomed for the night.

So here I sit, we just finished the Machine Problem and it is 5:30 in the morning. Jay and I are definitely skipping lab this morning. I offer proof that procrastination is bad, unless you are a professor.

*This image is an example of what happens when you study, program, or even think too much, too late about COS 250.