I was going to ask for a binary watch: http://www.thinkgeek.com/gadgets/watches/6a17/ Maybe I'll ask for my birthday.
I was going to get the girls a musical clock, maybe I can still work it out. http://www.seikoclocks.com/collections/melodies.aspx
This is a nice shirt: http://www.thinkgeek.com/tshirts/frustrations/5aa9/
As are these:
http://www.thinkgeek.com/tshirts/science/6e7e/
http://www.thinkgeek.com/tshirts/coder/5d6a/
http://www.thinkgeek.com/tshirts/coder/595d/
http://www.thinkgeek.com/tshirts/sysadmin/280d/
http://www.thinkgeek.com/tshirts/frustrations/374d/
http://www.thinkgeek.com/homeoffice/stickers/28e6/
http://www.thinkgeek.com/tshirts/science/60f5/
What's wrong with me you say? I'm a Unix Platform Engineer. That and I have been known to be grumpy...
What I really need are a few pairs of pants, if anyone is REALLY keeping score)
Saturday, November 26, 2005
Wednesday, November 16, 2005
Gotta love management
Last night I got the following email:
"With the introduction of blades and the discussions surrounding virtualization, there has been confusion concerning vocabulary. Last Thursday, a group of engineers, product managers and architects got together to try and come to some consensus as to terms. The results are summarized below and represent a start. I am going to present the terms as I remember them. If clarification is needed, please feel free to comment. The intent is to get everyone talking the same language.
Thanks,
Bill.
Chassis – this is the physical container that houses the mother board, cards, etc.
Examples include DL380’s, blades, etc.
Enclosure – enclosures house many chassis’.
Server unit – the operating environment slice in which application instances can run
Logical dns – represents an aggregation of server units."
I replied as follows:
"It took a group of engineers, product managers, and architects to come up with that?"
What followed was a half day worth of email from all locations starting with a 2 page reply with explainations about their thinking behind each name, etc. (From an architect. My manager thought it was funny...) Then the CIO chimed in a couple of times, other engineers chimed in, and the architect replied to all of them. One of the documentation people tried to create a diagram, but he got it wrong, the CIO jumped all over him, and then he had to talk to an engineer, get the diagram fixed, and resend. One of the other architects replied that his head hurt worse now than it did when he was in the meeting making the name settings.
It finally ended when one of the engineers sent the following:
"RED NECK Vocabulary
Chassis - Underneath my pick up
Enclosure - Top on my Jeep
Rack - How big them horns are on a slab of meat
Blade - That knife I killed that varmit with"
I was just being sarcastic. There really didn't need to be any reply back to me in the first place. I guess that will teach them for saying "If clarification is needed, please feel free to comment." During the middle of the day, I sort of regretting starting the thing off, but given the chance again, I'd probably do the exact same thing again...
"With the introduction of blades and the discussions surrounding virtualization, there has been confusion concerning vocabulary. Last Thursday, a group of engineers, product managers and architects got together to try and come to some consensus as to terms. The results are summarized below and represent a start. I am going to present the terms as I remember them. If clarification is needed, please feel free to comment. The intent is to get everyone talking the same language.
Thanks,
Bill.
Chassis – this is the physical container that houses the mother board, cards, etc.
Examples include DL380’s, blades, etc.
Enclosure – enclosures house many chassis’.
Server unit – the operating environment slice in which application instances can run
Logical dns – represents an aggregation of server units."
I replied as follows:
"It took a group of engineers, product managers, and architects to come up with that?"
What followed was a half day worth of email from all locations starting with a 2 page reply with explainations about their thinking behind each name, etc. (From an architect. My manager thought it was funny...) Then the CIO chimed in a couple of times, other engineers chimed in, and the architect replied to all of them. One of the documentation people tried to create a diagram, but he got it wrong, the CIO jumped all over him, and then he had to talk to an engineer, get the diagram fixed, and resend. One of the other architects replied that his head hurt worse now than it did when he was in the meeting making the name settings.
It finally ended when one of the engineers sent the following:
"RED NECK Vocabulary
Chassis - Underneath my pick up
Enclosure - Top on my Jeep
Rack - How big them horns are on a slab of meat
Blade - That knife I killed that varmit with"
I was just being sarcastic. There really didn't need to be any reply back to me in the first place. I guess that will teach them for saying "If clarification is needed, please feel free to comment." During the middle of the day, I sort of regretting starting the thing off, but given the chance again, I'd probably do the exact same thing again...
Tuesday, November 15, 2005
A quilt? That was all that was needed?
The girls never go to sleep at night. Instead they have a 3 hour party, until they one at a time collapse, exhausted.
Mary got her new quilt last night from her grandma. Last night they went right to sleep. Amazing.
Mary got her new quilt last night from her grandma. Last night they went right to sleep. Amazing.
Subscribe to:
Posts (Atom)