Apple’s latest – the iTit

So, today I was at the Kingsmead scorebox for day 5 of the test between South Africa and the Aussies. We won’t mention the unfavourable result (from a South African perspective, that is), instead I’m going to draw your attention to something that one of the journalists in the press box found in the morning session, and who consequently had everyone who was in there at the time in stitches of laughter.

Upon Googling it now, I found that this one has been doing the rounds on several other blogs for a while now, and I have no idea who the original source was – this blog was the first thing that came up in my Google search results, so that’s what I’m putting.

Apple Computer announced today that it has developed a computer chip that can store and play high fidelity music in women’s breast implants.

The iTit will cost $499 or $599 depending on speaker size.

This is considered to be a major breakthrough because women have always complained about men staring at their breasts and not listening to them.

The AOL Translator

Take a look at this – it takes what you write and converts it into the manner that a 12 year old AOLer would write it.

I tested it with the following post on my forum:

Ron needs an EPIC fail for his feeble attempt at camping, or what ever he wants to call it, he might as well have gone paint balling on his own, i am sure it would have been the same for him.

… and this is what I got back…

RON NEDS AN 3PIC FALE FOR HIS FEBL3 AT3MPT AT CMPNG OR WUT 3VER HE WANTS 2 CAL IT HE MIGHT AS WEL HAEV GONA PANET BALNG ON HIS OWN IM SURE IT WUD HAEV BEN DA SM3 FOR HIM!!11!1!1! OMG WTF

I now have a new favourite toy. πŸ˜€

Ron’s Fun Friday

Get to work, minding my own business – then, at 10am, the local transformer box blows (AGAIN). I was working on a critical update to one of my apps at the time that just HAD to go live today. So, no problem I thought, I’ll just take my work computer and go home to finish it. I get home, and found that for some reason, my stuff wasn’t synching between my computer and the dev work server as it should have been – all my stuff was on the dev work server.

I then phone my network admin, and hear that he and the support people are the only ones left at the office – everyone else had buggered off (bearing in mind that we had scheduled load shedding at 2pm, and this looked like it would take a while to fix). He says no problem, come and get the dev work server (with EVERYONE’s dev work on it, mind you), and take it home with you. I’m like “are you SURE????”, and he’s like “no problem”. So, I drive the 3km back to the office, pick up the server, get the admin password for it, and off I go home again, connect both PCs up to my network, and transfer my stuff to my work computer.

It doesn’t take me long to finish the code changes that I had been planning, but now I have a new problem – my code needs to go onto our daemons server at our server farm at IS in Umhlanga – and I can’t go through the office network, because the UPS died five minutes after I left the second time. Once more, I phone my network admin. He tells me that there’s a back way in, and tells me all the details. I upload my code to the server, and test it – it worked first time, thankfully.Β  πŸ˜›

As I finish testing, one of the support people phone me to tell me that the power is back on. So, both computers get loaded back into the car, and back to work I go to put them back. We plug the dev work server and my work computer back in, and I quickly send off a few mails that needed to be sent, as our 2pm scheduled load shedding is about to happen. Sure enough, it happens. At this stage, I decide “bugger it”, and head off to the Pavillion to get some lunch and kill some time.

After Steers, I pop into Look and Listen and pick up two trance CDs (the same one I got for Palu but this time for myself, and another one). I browse around the various shops in the Pav, looking for something to keep me interested. Eventually, I look at the time. 4:15pm. I have to be at Kingsmead at 4:30pm as I’m doing the scoring for Cricinfo for the Pro20 final. So, off I head, only to be caught in the mother of all traffic jams at Warwick Junction. I eventually work my way through, and get into the Kingsmead scorebox at 4:50pm. Fortunately, my rather late arrival wasn’t a problem, as everyone else got caught in the same traffic jam.

So, I sit though 40 overs of a really good cricket match, which the Dolphins lost narrowly, get invited to drinks in the President’s Suite afterwards (nothing alcoholic for me – still had to drive home), and head off at 10:00pm thinking “what else could possibly happen today?”. As it turns out, there was an accident on Spaghetti Junction that had happened moments before I got there, and as it was pitch black I only saw it at the last minute (and, Murphy’s Law, it’s in MY lane). I don’t know how I managed to avoid running into the crashed cars and keep control.

So here I am, at 11:10pm, finally chilling out at home. Won’t be online for much longer, as I’ve got an early morning tomorrow…

How to play Supreme Commander

Every now and then, I give Supreme Commander a go. This is typically what happens:

1. Make sure Andrew is on your team.
2. Let Andrew do the actual hard work of hunting down the opposition. After all, he’s way better than you.
3. While the above happens, act all emo and stay in your little corner… while building nukes.
4. Wait for Andrew to do a bombing run and disable the anti-nuke defences.
5. Initiate a nuclear winter across the map.
6. …
7. PROFIT!

Hey, it works when Andrew and I are playing against the AI… πŸ˜‰

(Yes, yes, I know… I’m going to have to think up a better strategy when I play human opposition. I’m working on that.)

A little programming poem

This was posted in one of the Facebook groups that I’m a member of, and I can’t pass up posting it here.

Major bugs have little bugs, which, being fixed, can cause ’em.
And little bugs from tiny bugs, and on it goes ad nauseam.
The bigger bugs themselves can be pernicious, tangled creatures;
So suck it up and ship the code and we’ll just call them “features”.

LOLCODE!

I’ve just been sent a link to an emerging programming language called “LOLCODE“, which is by far the funniest thing that I’ve seen for a long, long time.

Here’s an example of a Hello World program written in LOLCODE:

HAI
CAN HAS STDIO?
VISIBLE “HAI WORLD!”
KTHXBYE

Or simple loops:

HAI
CAN HAS STDIO?
I HAS A VAR
IM IN YR LOOP
   UP VAR!!1
   VISIBLE VAR
   IZ VAR BIGGER THAN 10? KTHXBYE
IM OUTTA YR LOOP
KTHXBYE

Or file and exception handling:

HAI
CAN HAS STDIO?
PLZ OPEN FILE “LOLCATS.TXT”?
   AWSUM THX
      VISIBLE FILE
   O NOES
      INVISIBLE “ERROR!”
KTHXBYE

Some people obviously have WAAAY too much time on their hands… πŸ™‚

How to play Natural Selection.

While I’m on the subject of games, here’s a how-to I found on how to play Natural Selection. It applies to a few other games that I know of as well.

Must-know etiquette for being accepted on public servers.

On the marine side…

Voicecomms Never, in any circumstances, use your microphone when anybody is shooting, building, commanding, welding, or jumping. By transmitting your futile bytes of useless information (examples: I’m in the hive, give me a pg now!/I need a weld, please), you are clogging up the game sound of the professional players, thus hindering their ability to rambo and rack up high scores. Every single sound that you make will cause fifteen cloaked skulks to spawn behind them, thus guaranteeing death.

If it’s a matter of real-life life or death, then you may be permitted to transmit as long as the professional players are in the spawn queue (which is your fault because of the previous transmission). When you transmit, you must ensure that you’re:

a) On a T3 connection, because every byte counts
b) a natural English speaker, without any kind of accent (be it national or regional)
c) pronouncing every word and syllable perfectly without stuttering, interruptions, feedback, or background noise.

If there are any imperfections whatsoever you will be instructed by the professionals to leave the server, fix your mic, buy a new mic, buy a new accent, buy a new voice, or go and play on a ‘german haxor server’.
If you need welding but you die, it is clearly your fault for not asking people over the voicecomms. When near an empty resource node, it is also your fault if you don’t call for a res node (not allowed to use comms for fear of causing death). When you ninja up to a hive and need a phase gate, you are to blame if you don’t call for the gate, since the commander has you all muted for obvious reasons.

Commanding
The command chair is a somewhat important tool used by the marines to win or lose games. If you get into the commander chair for the first time, you will immediately be to blame for every single game loss that day, regardless of which side loses. When the server crashes later from all the abuse, that will also be your fault. If you’ve never commanded for a national NS team, you must delete the command chair model from your NS directory, in case you accidentally face it while humping the armoury and get in. Even if you log out straight away and never touch it again, the next commander will blame everything that goes wrong in the following game on you. The loss will be put down to ‘that nub idiot that got in the chair at the start’.

If your commander dies for whatever reason during the game, you will be instructed to get inside and beacon the marines. If you get inside only to find the observatory destroyed, this is your fault. You must relocate to a horribly obscure place so that the game will drag out another 5 minutes.

When commanding, make sure to follow every single marine 100% of the time, all at once, even if they all split up. If you find this difficult try buying multiple monitors and find a way to break the birdseye view. This will enable you to medpack the marines that get parasited once and call for medical attention. Be sure to drop resource nodes at least 1 minute before the marines get there, otherwise you will be deemed ‘slow and crap’. Make sure you pay especially close attention to the professional players, and make sure there are always at least 30 medpacks and ammo containers around them, in case they ever get bitten (which is your fault).

If you plan to command a game, make sure you already have armour 1 upgraded before you first reach the command chair. If you don’t, you are again deemed ‘slow and crap’. Don’t forget to drop ammo around the armoury so the professionals don’t have to copulate with it. If at any point during the game someone needs welding, it is your fault for not dropping welders.

Within 20 seconds you should have phase tech. Another 10 seconds you should have the majority of the upgrades from the armslab, except catpacks which should be ignored because they would make you ‘slow and crap’, which is ironic since they do the exact opposite. Within 1 minute you should have 15 res nodes, 2 hives, and jetpacks.
Be sure to pay attention to the 42609872 medpack/order/ammo requests that take up all 512meg of your ram and crash your computer when a marine has to wait more than 2 seconds for your attention. As the delightful woman-ai-marine-commander-woman-girl will happily inform you, you must hit your jump key to go to the alert. This will probably move your view to a marine that’s just died, or one in base that’s humping the armoury for a medpack and has little patience. If you’re lucky, the marine will still be alive, and will be trying to knife a fade. He will die, and blame you for lack of medpacks. Sometimes this alert will take you to a squad of 5 marines who are crouching in a cloud of poison gas. Make sure you med them every 0.5 seconds in case they go below 90hp.

If you build a turret factory anywhere, you will be proclaimed a ‘nub’. If you upgrade it though, the ‘nub’ status is removed. This is a handy way to kill hives. Never electrify anything or build any turrets, because they are obviously worthless and inferior to 7 marines that can’t aim. At the same time, make sure you have at least one hive ‘locked down’ so that no aliens can take it over, which you must accomplish using neither mines (too expensive and get placed on your chair), or turrets, or indeed marines (they’re all in double staring up at a vent that a lerk was in 9 minutes ago).

If an onos appears, prepare for massive breakage of the various ‘voicecomms’ rules. Make sure you medpack the lone shotgun marine that goes to solo the onos.

If you lose any res nodes, make sure you inform your team (not using voicecomms, remember) that the node is dying. When no-one responds and you lose the node, this is your fault because you didn’t tell anyone. However, you cannot electrify it because that makes you ‘new’. Make sure you always have at least 500 resources, so that people can have a jetpack for the readyroom on the offchance that you win. If you lose, you will be flamed with added petrolium every time you even look at the comm chair on that server, so change your nick and hope to God that no-one got your steamid.

Playing a marine
This is one of the easier roles to play, because you can be completely useless and crap and it is still somehow the fault of the commander. Be sure to delete your waypoint sprites so you have an excuse not to follow them, wander aimlessly around the map asking for weapons/jetpacks/ammo at various time periods in case your commander forgets you. If he ever takes more than 2 seconds to respond, flame him, call and admin, and eject him. Tell him he’s a ‘cs nub olol’ and he will surely take offence.

One thing you must be careful of, are the professional players. You must never go near them, just in case you steal their kill. If you save the life of such a player, surrounded by 16 onoses with only a knife out, you will still have stolen his kills. However, if he dies it is your fault (and the fault of the commander). Stay well away, because if you block them, block their shots, or make any noise whatsoever, you will immediately give away their location and be the cause of every death for the following week.

Always go and find new res nodes to build. When you call for orders, prepare to be ignored for 3 minutes. When the node is finally built, you must somehow simultaneously build another node (some distance away) and protect that one at the same time. If either get bitten once, comm will recycle base and blame you for the loss.

Make sure you follow waypoints, even obscure ones that are randomely given to you because the commander is using the ‘select all marines’ button. If you’re sitting in a hive that’s going up waiting for a phase gate and he medspams you so the aliens hear, it’s your fault for being low on health.

If you see a phase gate, you must phase through in case the other end is being attacked, so you can get raped by a bunch of hungry skulks. At the same time, if you see a phase gate you mustn’t phase through, just in case there’s another, more important gate going up elsewhere.
You must be in base, at every node, and every hive, and killing aliens, all at the same time. If you can’t multitask to this extent, you are a useless cs player.

Come to realise that the comm screaming ‘kill that fade omg 1 bar left wtf useless die argh recycling’ means that you failed to kill the fade, and it’s entirely your fault. Negate umbra, 5 onoses, 34 gorges, a hive, and the fact that you had no ammo – it is entirely your fault. If any teammates were there, they will also most likely blame you, for blocking them.

On the alien side…

Voicecomms
Similar in most ways to the rules of the marine voicecomms, you must always report every marine everywhere (professional players don’t parasite in case it gives their position away), because any hive ninjas will be your fault. Do this without speaking at all, but if you type you will be deemed ‘too slow’.

Gorging
When the game starts, ask people what chambers they want. When you get no response, drop movement, defence, and sensory chambers. As difficult as this may be with only one hive, you must find a way to please everybody. Despite only starting with 25 res, you must somehow build all 3 of each chamber, with only 1 hive/node. At the same time, you must heal everybody, take their bullets, and put up another 2 hives. If you build a single offence chamber, you are a ‘crap nub’ and will most likely be flamed off the server. When the marines jetpack kill a hive, it is your fault for not building any offence chambers.

Be sure to ‘lame up’ every single room and corridor in the map. If marines ever see any of your hives, you will lose and it’s entirely your fault. At the same time, don’t build any structures whatsoever, because they will block all the professional fades and they will die. Again, your fault.

When you’re sitting a hive telling your teammates that there are marines building a phase gate, wait 3 minutes. When you lose the hive, expect death threats from your teammates for not saying anything.

Playing an alien
Make sure you parasite every single marine, otherwise you will cause the death of every single teammate. Also, make sure you never parasite any marines, in case a professional skulk was about to ambush him. You’re not allowed to move in NS at all as an alien unless you can bunnyhop perfectly.

If you ever die, ever, you are accused of feeding marines.

If a professional player dies, it is your fault for not building enough chambers/ocs/hives/nodes so they can re-fade. Alternatively, it is your fault for building too many of these things so that they block said fade.
If you’re not a national team chamption fade of godly proportions, you are not allowed to fade. You must practice fading in combat, which will make you get used to playing with every upgrade. If you ever die as a fade in classic, the entire game loss is your fault. If you cause them to beacon, fail to kill their advanced armoury, fail to spend 3 minutes eating a res node, then expect your entire team to f4 because you’re so useless.
If you ever have more than 3 res you are a res whore. If you ever have less than 3 res you suck, because you’re not building enough nodes or killing any marines.

When moving around the map, make sure you are never within 90 yards of any other aliens. If you hit a mine and a professional player dies to a turret on the other side of the map, it is your fault. If for whatever reason you do fade and you die to 32 fully-upgraded jetpack hmg marines with catpacks, you are clearly a noob. The game loss is your fault.

If you somehow win the game as aliens, you must either egg or suicide at the end, otherwise you’re deemed a ‘nub.

General Strategies

Always build MCs first. This means that players who like to lerk a lot are unkillable. It also means you can MC rush the hive which marines inevitabley take, which usually fails because most people are afk or attacking marine start pointlessly. When you find yourself the only alien to have MC’d through, you must kill every single marine and structure yourself. If you fail, the game loss is your fault.

If you onos, you must never die. If the aliens see an onos die, ever, the game is lost. The conditions are unimportant, just make sure you never die, even if that means hiding under the hive for the entire map.
If you’re commanding, the moment you take a hive, the aliens will whine about lockdowns. If you then take another hive, the aliens will whine about the game being ruined.

As their desperate fades kill every single marine and res node you have, while killing the advanced armoury and armslab in base, you must ‘finish them’ or you are accused of taking too long. Even as they pointlessly MC rush new hives delaying you, you should still be expected to win. 9 lerks sitting next to MCs spamming horribly large amounts of gas into the only entrance to the hive is no excuse for marines to delay while getting HA, they are clearly new for failing to win the game quickly.

If you find yourself winning as aliens, be sure to completely ignore the 3 jetpack HMGS frantically defending marine start while ‘finishing them’. You are expecting to kill every structure in their base while being shotgunned by 8 marines who have supposedly given up and are not even trying anymore, while they ninja a PG in your 3rd hive and take it down, again complaining that you’re not finishing it fast enough.

Maps
Regardless of which map you play, always relocate to double. Even if there isn’t a double res, pretend there is one. If you really can’t manage this, find the most horribly cramped, dark, damp, dank, ghastly corridor in the map and relocate there. Be sure to arrange your structures so that a freshly spawned marine will have to spend 8 minutes twisting their limbs around various turrets and armourys in order to get out of base. Don’t drop any mines either.

Make sure you always secure cold turn on Ayumi, because if you don’t then you’ve ‘lost the game’. At the same time, pretend you didn’t secure it, because if you do then you’ve ‘ruined the game’. Subtley attempt to lock down 2 hives without actually locking them down, otherwise you will be declared ‘lame’. On eclipse, always rush computer core. Once you have 530 turrets in there, tell the one-hive aliens that they have every chance of taking it back, and they should ‘adapt’.

Don’t forget that the map can always be blamed for any loss, any situation, or any server crash. Whatever happens, it is because it was a ‘shit map’.

Remember: People with icons are obviously and naturally much better at NS than people without. Regardless of what the icon represents, you must always stack the team with the most icons. This will create short predictable boring games, that everyone loves. Whenever you die, tell your opressor to fix his rates, to stop ‘warping’, and the reg is shit.

And most of all, have fun!