Tag Archives: crash

Earl Rose writes off Ooskus Fish & Chips

Remember I noted that Monday morning’s Die Burger carried two local stories of interest in its pages regarding events over the past weekend?

Well the first had to do with Chantelle’s 80 year old great uncle Hubert Montgomery who got knighted by the Spanish monarchy for his lifelong contributions and commitment to the sport of weightlifting. However, this played second fiddle to the front page story, which if you are already not quite a fan of the guy, makes for quite a good chuckle.

So at more or less 03:00am last Sunday morning, an allegedly completely drunk out of his mind Earl Rose, a professional rugby player who hasn’t been playing all that much rugby this season, managed to come racing at full tilt down Sir Lowry’s road in his fancy sponsored black BMW, with his wife Amor seated beside him.

Unfortunately for him, he opted not to hit the breaks as he came to the end of the road, a t-junction mind you, and instead raced head first into the unfortunate beloved Ooskus Fish & Chips shop, a Gordon’s Bay establishment that has been around for 38 years mind you. (In other words, its not as if this t-junction with a shop at the opposite side of it just cropped up overnight!)

Also, note that the luckless Mr. Rose was shirtless at the time.

Classy.

Needless to say, the owners of Ooskus are less than impressed, and undoubtedly, their insurance as well. After all, I think it is just short of a year ago now, when poor old Ooskus’ kitchen burnt out thanks to a fiery accident. So luck is definitely not on their side.

It is however on Mr. and Mrs. Rose’s side though. If you look at the damage the crash caused, they’re pretty lucky to have walked away from this unscathed!

(Chantelle grabbed these snaps on Sunday morning on her way to work).

Good news though. Ooskus is trading from the owner’s home which sits next door to the devastated shop, and from the look of things, repairs to the main shop are already well underway.

Shorts: Move, Crash, Sleep, Birth

(NOTE: This was meant to be published last week – but thanks to a “kidnapping” of me by my wife for a surprise birthday celebration weekend away, I only get to post it now! :P)

So life has been quite busy on the work front as of late, not because of work (well okay, there have been a few crises to deal with) but more precisely thanks to our latest big move, shifting the entire operation from Unit 4 in the building down the line to Unit 1. This of course means that the dev team is no longer trapped in a box in a garage under the main office (though in fairness we did have a table tennis table to keep us occupied) and it must be said that the new office that we all now co-inhabit is a lot more airy and spacious than the previous one we came out of. I’ve got a nice seat with a good view and feeling of openness, so I’m pretty happy about the whole affair.

But man what a mission. Unlike the last time when we just moved the dev team downstairs and before that when we moved from the boss’ house (we didn’t have much existing equipment to move), this was far more strenuous and with a whole lot more heavy stuff to lug across!

Unfortunately things didn’t go all that smoothly and we’ve been plagued with connectivity issues since (which follows on the week of the frustrating Seacom debacle which also kept us offline), having lost a network card on the one proxy machine and more importantly, the diginet router, a hell of an expensive piece of equipment to replace. As it is, I’ve had to play deliveryman and pick up the replacement from a house in Somerset West, having to go there three times, the first time to pick up the router, the second time to return it to have a card in it replaced (at 22:00 in the evening!) and then one last time to return the spare cable we were loaned after the second visit! To make matters worse, there were some account stuff ups from Telkom’s side as well, meaning that this entire week we’ve pretty much kicked off each and every day with connection – bloody frustrating as you can imagine!

Oh, and the new project manager arrived. Pretty cool guy and I am looking forward to working with him as he strive to implement a more structured, agile development methodology moving forward.

It would also seem that winter is now well and truly beginning to stretch her cold limbs as we’re finally being hit with bucket loads of wind and water – which always seems to trip up the less competent drivers. I’ve already spotted two fender benders happening right in front of me because the driver behind a) isn’t concentrating and b) doesn’t increase his following distance in these wet and slippery conditions.

That said, I myself nearly put a little dent in Gina G., not because of the weather conditions but rather because of a momentary lapse in concentration. I had just pulled into a parking bay in the underground parking at the gym and was leaning over to collect my card and access keys when I realised that the car was actually rolling forward – she was still in neutral and I had forgotten to pull up the hand brake!! I jumped on the brakes and stopped her dead in her tracks, literally a centimetre from the wall and a nasty pipe which would surely have left a bit of a ding in my beloved Getz.

(Oh, and I’m pleased to announce that she’s finally becoming less greedy in terms of her petrol consumption – seems to be moving around in the Jetta’s consumption area at last!)

Now on to my completely next arbitrary topic for this quick post of shorts deals with the fact that I completely crashed on Wednesday. I haven’t been getting a lot of sleep lately (really my own fault, so no one to blame – stupid desire to tinker on websites) and as we moved into the afternoon I suddenly found myself falling into a complete and utter state of exhaustion, literally both mentally and physically fatigued all at once. So instead of driving through to karate, I found myself turning in at our flat, where I hit the bed, woke up when Chantelle arrived home at 08:00, ate supper that she made and then went back to bed. Seriously, I have no explanation for it, but the extended period of sleep did seem to help somewhat for the rest of the week.

Okay, what next? Ah, Andri gave birth this week to a healthy little baby boy, Arum Reid Jack (I’m not sure if it is Arum like in the flower or Aram. I’ll get back to you on that one). Chantelle has already been to see the proud parents (this is their second one) and I’m sure I’ll get around to seeing the new tyke sooner than later. Shame, little Zandea seems to have recovered from her bout of illness that saw her rushed off to hospital and poor Zania spending about three nights sleeping there! But man, everyone around seems to be pregnant at the moment. Michelle (Ollewage) gave birth just a short while ago to a beautiful little boy (who looks like his dad) named David, Michelle (Oosthuizen) has just reached the halfway mark in her pregnancy, Andy has come out and officially announced her pregnancy!

So maybe it is no wonder that Chantelle and I also feel that now is the right time for us? ;)

Anyway, I think that about wraps it up for life at the moment, so now you can’t complain about not being in the know! :P

PHP: Simple Try Catch Example

With object orientated languages came the concept of the try-catch block to better manage exceptions and application crashes, and from PHP 5 onwards, the popular web server-side scripting language too adopted this ideology.

By placing code which stands a possible chance of failing within a try block, you are alerting PHP to the fact that should it fail to correctly process that chunk of code, it needs to pass control over to the code sitting within the catch block definition and then continue running after that backup code has been executed.

To see this in action, consider the code below:

try {
    $error = 'Throw this error';
    throw new Exception($error);
    echo 'Never get here';
}
catch (Exception $e)
{
    echo 'Exception caught: ' . $e->getMessage() . "\n";
}

Now admittedly in the above code block we are cheating a little by forcing the script to ‘crash’ by throwing an exception, but in the usual case we’d have pretty normal code in there like opening a file perhaps. Should it execute correctly, the application would simply continue to run, but had it failed, like we’re forcing it to do in the example above, PHP passes control over the exception handler code sitting in the catch code block, this time performing a simple echo out of the trapped error message.

So in other words, a simple but powerful tool that any current era developer should be making use of in order to better ensure the stability of their scripts.