Improving the mating prospects of the Systemus Administratorus
Long standing joke: The sysadmin was in the pub with his girlfriend and …
Those of us who work in the IT industry will be familiar with the stereotypical geek; equipped with gadgets, fluency in several programming languages and more attuned to the processes of a RHEL box than the female of the species. Their chances of reproduction are low (discounting alien abduction, which of course if you know any sysadmins is something that has to be explicitly mentioned).
I believe this situation is less than desirable for several reasons;
- Most sysadmins have higher than average IQ, and when you get to know them, they usually have an (albeit warped) sense of humour
- Look at the alternative: seriously, the way things are going us chickies are going to have to fight for space in the bathroom with the waxed, plucked, shaved, perfumed, buffed and polished metrosexual men gracing the wine bars and coffee houses. Pah! Less wax, more coding.
- Dress sense is overrated. If a sysadmin could co-ordinate they would have chosen fashion design as a career (kill me now). There is nothing wrong with black. On black.
- In twenty years’ time when your house is networked and your toilet communicates via Firewired USB enhanced terabyte LAN to your toilet paper, who is going to fix everything? Buffboy? I don’t think so!
Well, I hear you say, it’s all been done before in Beauty and the Geek. Supermodels and Geeks pitted together in tasks designed to stretch the skills (and in some cases the bra straps) of both groups.
They’re just not thinking about this clearly. The problem is that Woman has not been documented in UML!
So, for the benefit of all sysadmins out there;
class Woman
static changeMind() // this method can be called statically - it requires no instantiation
private moodSwing()public height;protected Friends; // aggregation from child class Friendsprivate age;private weight;
Can anyone think of any amendments ?
