Monday 10 May 2010

Head elsewhere

Haven't posted for a few days, life has been kicking me around a bit but I'll survive.

The Gods of IT inadequacy have thankfully had the grace to leave me alone.

I need a break, a holiday, just some time to get away and clear my head but it isn't going to happen.

GrumpyGeekDad is definitely not a happy camper :(

Wednesday 5 May 2010

To end the day...

This is brilliant!

http://news.bbc.co.uk/1/hi/england/gloucestershire/8660449.stm

I want to know when they are going to put these up in my city!

Innuendo bingo

Ops Director (female): Is the new fax machine working?

GrumpyGeekDad: Yeah, it should be.

Ops Director: Cool, can you come and show me where I sho... I don't really want to say that to you, do I!?

GrumpyGeekDad: Probably not *Laughs*.

This just in...

I was sent this email by the world's most arrogant field Sales Guy...

"GrumpyGeekDad

Dictator has asked me to ask you to write a response to the following question which will form part of a proposal.

How do the servers work and how is data stored?

Could you do this this morning please?

Regards,
ArrogantFieldSalesGuy"

Just how deep would he like me to go with this? Is the target audience for this proposal tech savvie? I mean I used to teach this stuff. I'm thinking of starting with this:

The Application on the remote device receives fix information and compares the data to a set of given criteria to decide if the fix is worthy of reporting. Once worthiness is established the data is encapsulated by the Application and passed down through the stack to the Transport Layer where the appropriate Port Number, Window Size, and TCP Segment Number are added to the Segment header information. The Segment is then passed to the Network Layer where an upper layer Protocol Number, in this case 6 (TCP), a source IP address (the local device) and a destination IP address (the remote server) are added to the Packet header. The device then consults its own routing table to see if it knows of a local route to the destination IP address. It won't and therefore passes the Packet down to the Data Link layer where an upper layer Protocol Identifier, in this case 4 (IPv4), a source MAC address (the local device),and a destination MAC address (the local interface of the local router, aka Default Gateway) are added to the Frame header. A Frame trailer is also added including a Cyclic Redundancy Checksum (aka Frame Check Sequence). The device then converts the data into Bits (Binary Digits) and broadcasts them onto the network medium.

DON'T ASK STUPID FUCKING QUESTIONS!

Yes, I'm ranting, I know, but it's turned into one of those mornings.

Tuesday 4 May 2010

In true Geek style...

Happy Star Wars day!

The long weekend was a welcome break, looking forward to the next one at the end of the month!

Friday 30 April 2010

4 minutes to go

And it's off for a 3 day weekend. I need it.

That didn't take long...

You are the head of your own little empire, you take on a new field sales guy who has come from a printer/copier company. You decide that your head office could do with a new all singing, all dancing, multifunction laser network printer/fax/copier with an extra booklet unit add-on.

Do you:

A) Consult your GrumpyGeekDad about the new purchase. Discuss where the unit will be located within the office (this thing is 4' x 2' x 4' and needs power, network and phoneline connectivity). Discuss which one of the two physically disparate networks the device will be connected to and therefore which of the company's employees will be able to use it?

OR

B) Not bother even mentioning it to GrumpyGeekDad. He loves surprises and will relish the challenge of having to deconstruct desks to make room, repatch several network points and guess which of the aforementioned networks this thing will be attached to (and therefore configured for) all while you are unavailable, somewhere between the 8th and 9th hole?

If you picked option B then thanks for that, I was bored stiff. I'll see you on Tuesday morning, boss.

*Shakes head*