G/B/D

It's been a long time since roho posted anything his journal involving "Something Good / Something Bad / Something Different" so I figured now is the perfect time for me to do so.

Something Good: Despite the insane number of hours I have spent behind a keyboard this week, my wrists have not bothered me once. I believe this is because I've been constantly wearing the IMAK "Smart Gloves" that I wrote about earlier this year. And when I say constantly, I mean it... I put them on as soon as I get into the training classroom, and I don't take them off until I drive home in the evening. I was afraid that I would have to take a few dozen Aleve to survive the week, but luckily that has not been the case!

Something Bad: It would seem that over the last 24 hours I have been clenching my jaw so much that I broke some of my dental work. When I got up this morning I found a small piece of dental bonding lodged under my tongue and could feel a "hole" in the bridging where there had not been one before. A quick peek in the mirror confirmed that it had broken apart. Now I get to dig up all my old dental plan information and try to locate a dentist!

Something Different: My commute every morning to class takes me past a giant billboard advertising "Diamonds Gentlemen's Club," which has a URL included below the prerequisite image of a "sultry" woman who is probably supposed to tickle my fancy. If I'm reading the URL right it is "www.diamondsxxx.com" Yeah, you know you're driving through a classy part of town when there's a billboard for a strip club beside the highway.

G/B/D

It's been a long time since roho posted anything his journal involving "Something Good / Something Bad / Something Different" so I figured now is the perfect time for me to do so.

Something Good: Despite the insane number of hours I have spent behind a keyboard this week, my wrists have not bothered me once. I believe this is because I've been constantly wearing the IMAK "Smart Gloves" that I wrote about earlier this year. And when I say constantly, I mean it... I put them on as soon as I get into the training classroom, and I don't take them off until I drive home in the evening. I was afraid that I would have to take a few dozen Aleve to survive the week, but luckily that has not been the case!

Something Bad: It would seem that over the last 24 hours I have been clenching my jaw so much that I broke some of my dental work. When I got up this morning I found a small piece of dental bonding lodged under my tongue and could feel a "hole" in the bridging where there had not been one before. A quick peek in the mirror confirmed that it had broken apart. Now I get to dig up all my old dental plan information and try to locate a dentist!

Something Different: My commute every morning to class takes me past a giant billboard advertising "Diamonds Gentlemen's Club," which has a URL included below the prerequisite image of a "sultry" woman who is probably supposed to tickle my fancy. If I'm reading the URL right it is "www.diamondsxxx.com" Yeah, you know you're driving through a classy part of town when there's a billboard for a strip club beside the highway.

1093 hours

Corporate WAN is experiencing serious borkage (that is the technical term for "it is acting broken" for those of you not in the network engineering field). In the last three hours there have been 134 notifications of sites flapping. This seems primarily isolated to our Keller locations, as they are sites with smaller pipes to the WAN (usually fractional T1s, although we do still have a few 56k leased lines out there). Network monitoring graphs are showing latency that has roughly tripled since 1600 to all of the sites hanging off the cloud.

Now, put on your chef's hat and prepare to mix the following ingredients:

One part "Nobody knows why this is happening"

One part "I am the on call engineer"

Three parts "I am the only one who knows how to troubleshoot this sort of stuff."

One part MCI/WorldComm

When mixed and baked after 8 hours of training you should be rewarded with a fluffy, dark-colored souffle. We call it "No Sleep For Feren Surprise." It is best served as the final meal to a dying man.

If you want to see what I'm staring at...
( Click here )

Love and only love will break it down

1093 hours

Corporate WAN is experiencing serious borkage (that is the technical term for "it is acting broken" for those of you not in the network engineering field). In the last three hours there have been 134 notifications of sites flapping. This seems primarily isolated to our Keller locations, as they are sites with smaller pipes to the WAN (usually fractional T1s, although we do still have a few 56k leased lines out there). Network monitoring graphs are showing latency that has roughly tripled since 1600 to all of the sites hanging off the cloud.

Now, put on your chef's hat and prepare to mix the following ingredients:

One part "Nobody knows why this is happening"

One part "I am the on call engineer"

Three parts "I am the only one who knows how to troubleshoot this sort of stuff."

One part MCI/WorldComm

When mixed and baked after 8 hours of training you should be rewarded with a fluffy, dark-colored souffle. We call it "No Sleep For Feren Surprise." It is best served as the final meal to a dying man.

If you want to see what I'm staring at...
( Click here )

Love and only love will break it down

ARGH!

Repeat it with me now, children, and be sure to speak clearly: I will not install Quality of Service on the corporate WAN router without first consulting Feren. If I do opt to install QoS on the WAN router without consulting Feren, I will not tell the router that a T3 circuit has a maximum bandwidth of 512k, because that's 1% of its actual bandwidth and will surely FUCK THINGS UP!

And now, in closing, I'm now going to borrow a bit from hightensile:

His coworkers were amazed by the amount of blood. His coworkers were amazed by the amount of blood.
His coworkers were amazed by the amount of blood. His coworkers were amazed by the amount of blood.
His coworkers were amazed by the amount of blood. His coworkers were amazed by the amount of blood.
His coworkers were amazed by the amount of blood. His coworkers were amazed by the amount of blood.
His coworkers were amazed by the amount of blood. His coworkers were amazed by the amount of blood.
His coworkers were amazed by the amount of blood. His coworkers were amazed by the amount of blood.
His coworkers were amazed by the amount of blood. His coworkers were amazed by the amount of blood.

ARGH!

Repeat it with me now, children, and be sure to speak clearly: I will not install Quality of Service on the corporate WAN router without first consulting Feren. If I do opt to install QoS on the WAN router without consulting Feren, I will not tell the router that a T3 circuit has a maximum bandwidth of 512k, because that's 1% of its actual bandwidth and will surely FUCK THINGS UP!

And now, in closing, I'm now going to borrow a bit from hightensile:

His coworkers were amazed by the amount of blood. His coworkers were amazed by the amount of blood.
His coworkers were amazed by the amount of blood. His coworkers were amazed by the amount of blood.
His coworkers were amazed by the amount of blood. His coworkers were amazed by the amount of blood.
His coworkers were amazed by the amount of blood. His coworkers were amazed by the amount of blood.
His coworkers were amazed by the amount of blood. His coworkers were amazed by the amount of blood.
His coworkers were amazed by the amount of blood. His coworkers were amazed by the amount of blood.
His coworkers were amazed by the amount of blood. His coworkers were amazed by the amount of blood.