Unforeseen power outage

The power went out at the office today when I had a pretty evil deadline to keep ahold of. Sure the power was only off for about 1.5 to 2 hours, but that was enough time to knock me off a delicately balanced schedule. I am not 1.5 hours down and about to go pick up Little Man from G-Ma D’s and G-Pa R’s. I will have to mea culpa to the PM and get everything to him before lunch tomorrow.

Unforeseen power outages suck.

To Recap:
I am insanely busy today
This is the digital painting I was working on
It goes to this fictional character on this rarely updated blog
I am hoping to start it updated more frequently, but the rest of the authors and I are in the midst of re-tooling a little bit
Most likely orange rice for dinner
I am tired of orange rice
More alphabet of SRH tomorrow
Cheers!

Time

Right off the bat, I want to let everyone out there in cyber land know that I have good clean teeth.

But on to matters of more import.

Time is a relative thing, but no matter how relative our sensations of the passage of time, things take time to get done. I do not know how to emphasize this enough to some of the knuckleheads that I have to work with. It has come to my attention, yet again that people managing projects think that the work we do magically takes no time. It takes time to convert files from what we use and print from, to what they can view and print out. It takes time to convert paper scaled maps to be ready for viewing on the web. Sometimes it take an inordinate amount of time to change the color of some text. The file sizes that we use are ginormous because the density of data associated with our tasks at hand are typically rather, err..., well..., dense.

Sometimes we run up against actual physical production time limits. Say some one wants 200 copies of 14 graphics. We have a printer that can spit color pages out at a rate of 11 per minute. After we get the file into the printer, that comes out to about 4 hours 15 minutes of physical printing time (if we don't slow things down went changing toner, toner refuse bins, paper, fusers, etc...) with no complications at all. Typically, the job requires some sort o presentation of those graphics in a format more orderly than loose sheets of paper, so let's say that the graphics need to be inserted into a larger text document and then spiral bound. It takes around 20 minutes per binding. So after the graphics have been printed we are still looking at an additional 4 hours and 40 minutes of collating and binding time. Just for production alone, we are at 8 hrs and 55 min, more than one full work day. Typically, each graphic takes about 15 minutes to open and get stored into the printer for final production, so that adds another 3 1/2 hours to just the production time. These are constant time sinks. Actual graphic edits take varying amounts of time on top of this 11 1/2 hours of production time for something as simple as a 200 copies of a report with 14 color pages.

Every time I explain this to a PM, they are always surprised at the actual amount of time it takes to finish things off in production, even after they have been finished pre-production. Sadly, this has been explained multiple times to a handful of PM's (I'm looking your direction, Asshat!)

Oh, well, enough of my ranting. My week is almost done.

Disharmonic convergence

So I am at work really late, or really early, pending on how one looks at it. There are 2 causes to my being at work at 1:20 in the morning on this cold Tuesday morning. It could only be the planets aligning to completely screw me for this to be where I am at the moment.

Firstly: One of those "Is there anyway you can make a map in a day?" requests crossed my desk around 9 am yesterday. The person in question is a middle man, of course. The project manager did not ask directly for me to spend an inordinate amount of time working on a map for a report that was supposed to go out later that day. That being said... when said PM is the head of your division and your boss's boss, you really have no option but to say, "Sure that should not be a problem. The sooner you can get me the data for me to start working the better." Workspeak for "Thank you, may I have another." The data in question does not show up until 11:25 am, whilst I was at lunch. Hey, a guy's gotta eat. Feverish work ensues.

The deadline is pushed back to Tuesday morning, through no mis-action on my part. So I decide that I will go home at a reasonable hour so I can play with my boy, and just get up stupid early to finish off the task at hand. My little one is riding high on a full 8 days of finally feeling well after about 6 weeks of ailments ranging from diarrhea to some kind of stomach fluish thing. This is foreshadowing for those of you not paying close attention, and it leads me to...

Secondly: While the little one is playing, right before taking his bath, the wife and I notice that little man is sounding a little bit raspy in his breathing. With a child with asthma, this is not a good sign of things to come. So we bathe the little one and then give him a breathing treatment right before we put him to bed. I run into work to finish the map, so in case Wheezy McAsthma needs to go to the E.R. tomorrow, I can take him without worrying about that stupid map for my boss's boss with time management issues (did the report sneak up on them? I think not).

I have completed a good first draft of the map, and now I am about to head home to my potentially sick little boy. I hope that it is just some congestion, but I am really worried that It is going to be worse than that. He's had 8 days of feeling good, what was I expecting? Wellness for 2 weeks? I was sooo foolish.