Archive for February, 2007

One of those…

This is going to be one of those posts… you know, the ones where you basically just list off a bunch of things you did recently.

Implemented VERP (Variable Envelope Return Path) for something I’m building at work

Spent friday afternoon walking around Kalk Bay with the GF, had supper at the Brass Bell and then went and paid our respects to Obs (where we met 3 years ago)… Obs has not changed at all in 3 years and it’s starting to be a bit like the uncle with the pony tail… just not cool any more. (Obs was probably never cool but it seems to suit certain people at certain phases in their lives). It’s never good for that phase to last longer than 2 years.

Went to look at Cape Gate on Saturday… it’s not worth it. Bought some thermal paste at Canal Walk… Took apart GF’s laptop, cleaned out 2 years worth of dust on the heatsink. Laptop fan no longer constantly spins at full speed and the laptop doesn’t reboot whenever you do something mildly complicated. Didn’t need the thermal paste.

Woke up on Sunday to find a dead DSL link light, once again reaffirming my opinion that it is impossible for anyone at telkom to carry out even the most basic of instructions without fscking something else up. This brought my proposed Amobia switchover forward to Sunday morning. Converted my Linux box to a router, installed squid… then had breakfast.

(Oh… I had my Amobia installed… It was such a non-issue that I didn’t even blog about it… I think I had it installed on the fourth work day after requesting it. Everything is working perfectly. When people finally get their ADSL lines installed they always seem to have this weird sense of self-achievement… like somehow they’ve “Stuck it to the man” and got their ADSL installed. That’s how twisted the state of telecoms in this country is… You dont walk out of the Pick ‘n Pay thinking “Yeah, I really showed them… I got EVERYTHING I wanted!”)

Spent the day hiking in Red Hill (Near simonstown)… Went to Kleinplaas dam and cooled off, walked back to where our car was. GF is now badly sunburnt (again…) Canadians!

Yours Aloe Vera Gellishly.

Comments

Want a job? Tell me what’s wrong with this html?

Maybe it’s the much talked about “brain drain” that’s retarding our country but I can’t seem to find people who know what they’re doing.

White BoardNow, I am by no means implying that we don’t have skills in this country… We have some of the most brilliant software and hardware people on the planet right on our doorstep — but that community doesn’t seem to be growing at a pace that is going to be able to keep up with the industry’s growing demands… and the industry is going to end up suffering because of it.

Case in point: I’m looking for Web Developers… The most fundamental need is a good understanding of the web and web standards… These things are the building blocks of web development; without them you’re destined to fart around in a world of buggy code and overcomplicated layouts.

Regardless of whether your coding language of choice is perl, python, php or *gasp* .Net, you need to know xhtml, css and web standards. Don’t tell me that your WYSIWYG editor did the markup and it’s therefore not your fault.

Want a job? Tell me what’s wrong with this. (I can quickly point out 15)

Update: I’ve had a few replies which I’m not posting yet because I want to try and keep the answers a little bit secret until I’ve gone through all the interviewees. The two people so far probably got A+ grades.

Comments (10)

How I learnt to love myself and stop supporting Telkom

My friend Vhata says I must not moan in my blog so I’ve decided to try and make this post as positive as I humanly possible. However, let me start by saying that Telkom is a filthy disease ridden whore.
roadlit

I could go and explain why I feel this way but honestly I can feel myself getting angry just trying to think of where to start… The important bit is this: I refuse to continue to support Telkom.

Until recently there really wasn’t much of an option when it came to broadband in South Africa. Telkom’s ADSL was the “best” solution, but like I said earlier, Telkom is a dirty whore…

Since Telkom owns all last mile copper the only other option is wireless. Traditionally the wireless market in SA was run illegally by unlicensed operators until a few got licences and the incompetent dogshow that ensued caused everyone, myself included, to decide that wireless was not a feasible solution (yet).

Enter, stage right, Amobia: a wireless communications company partnering with Frogfoot, a company I already have immense respect for.

Besides the pedigree that Amobia inherits from its Frogfoot connections, it’s also a company that is making a marked difference to the lives of the South Africans where it means the most… They’re connecting under-privileged schools; initially for internal communication, Open Source downloads and email, but ultimately to the Internet. They’ve done 35 and are on their way to 100. Not bad for a company a fraction of a fraction of the size of Telkom.

I’ve watched Amobia from afar for a while and two days ago, in the midst of another glorious Telkom blunder that left me discovering that Telkom’s systems really are a mystery even to themselves, I decided to jump ship and order an Amobia connection. Yesterday (the very next day) I had a technician in my house making sure that I would be able to connect properly and I expect to complete the paperwork tomorrow. It costs less per than Telkom’s ADSL and I know that Amobia doesn’t oversell their bandwidth so I should have a flawless, connected future, sans pigs, rats and filthy whores.

I’ll keep you posted.

Comments (4)

The 10 irrefutable rules of backing up.

(Ok, so maybe they aren’t irrefutable, but they’re 10 I came up with while writing the article. NB, These are obviously targeted at a business environment but the essence should apply at home too)

1. It can’t be manual

Humans are idiots at the best of times… we’re also forgetful and lazy. Any backup solution that relies on someone to backup various files to a CD or external hard drive just simply isn’t going to work too long unless you’re super-admin-person.

2. It has to be often

Backups that happen weekly just aren’t really good enough. Humans may be idiots but we can get a lot of work done in a week. There’s also that dreaded feeling of knowing that you have to put your brain through that same disgusting task AGAIN… that is assuming you know what you did in the last week. Daily backups are great, twice daily better.

3. It has to be off site or you might as well not do it

The reality is that most times backups are used to rescue idiot users who deleted the wrong version etc. It’s flipping awesomeâ„¢ that you were able to rescue Sue’s excel spreadsheet that she spent the whole morning on, but really, what are you going to do if your server room burns down… or gets stolen… If the backups are sitting on a removable hard drive or on a tape in the tape drive then your backups are gone. Sue’s excel spreadsheet wasted 4 hours. Not having the company data is often a death sentence for a business.

4. Have a backup of the backup

If all your company does is send off dlt tapes to a secure offsite security company then what are you going to do when you discover that the dlt tape was dirty and can’t be recovered? Sure, this is highly unlikely… but so is a fire in your server room… If all it was going to take to fix was a cheapass 500 gig external drive sitting on a rack then you’ll hate yourself for not having one.

5. Test your backups

This really leads on from number 4… Too many times I’ve heard someone say “I thought it was doing a full backup but actually…

6. Publish your backup policy

I’ve personally found out the hard way that the “server” backups didn’t include my code… If you publish the backup policy you at least give the lusers a chance at realising their impending doom.

7. Have backups aimed at mistakes and backups aimed at catastrophes

I’ve hinted at this in some of the rules above. You want to be thinking of backups with two hats on. First hat is “Rescue Sue’s excel from 5 hours ago“. Second hat is “OMFG the server room *actually* burnt down“.

8. Incremental is king

Ideally you want to be doing 4 Days (Mon,Tues,Wed, Thurs), 3 Weeks (Fri1,Fri2,Fri3), 6 Months(M1,M2,M3,M4,M5,M6), 2 Years (Y1, Y2). Yes, that’s a lot of backups… start at the beginning and see what you can do. Yes, it is paranoia, but businesses often need to go back for various reasons… Sometimes it will be as simple as finding an old database that suddenly became important again… or you might find yourself having to sift through mail folders after dodgy employees leave.

9. Dont skimp on cost

This one is particularly targeted at management. Backups are not valuable - they are priceless. If you force your techies to work with substandard gear, old tapes or pathetically slow systems you are putting your business at risk. There is no point in having a backup solution that is so slow that it can’t backup all the data in a day.

10. Grow with your needs.

Storage is not THAT expensive. Budget for backup systems growth just like you would budget for any new server hardware. If your needs can justify it, consider buying a full backup server. It is not a safe or productive solution if you keep on running over your tape limit and not getting a successful backup out the door. If individual departments have stupid amounts of media consider breaking them out of your main backup policy and develop a new one that suits them better… It might be that certain departments don’t need more than a few days incremental backups of their data.

In case you’re wondering what prompted this post… I’ve just set up a backup policy in my house. Our important data (Photographs, Thesises etc) gets stored/backed up on the server; that data is additionally stored (rsync) on a second HDD in case of primary HDD failure and then the most critical data is rsync’d up to a remote server sitting on the internet. This all happens twice daily and takes about 30 seconds due to the magic of rsync.

Comments (1)

Why some people just dont “get” the “Internet”…

(Alternative Title: When not to call someone a racist)

I am increasingly amazed at the interweb. People seem to not realise that the world is rapidly becoming more and more online to the extent that it’s probably likely that no matter who you are, your name, or your bussiness’ name is being Googled on a daily basis. Which brings me to the guy who called me a racist.

A while back a few of us went to a restaurant called Nonna Lina’s for lunch. The entire event sucked. The food was bad, the service was bad and the owner/manager overcharged us. I was so appauled I wrote a very strongly worded email to the restaurant and BCC’d a bunch of my friends.

Now a little bit about expectations… What did I expect from them? We’ll, to be honest I expected a reply… maybe even a sorry. I would have been very impressed if they had said something like “Hey, sorry you had a crap experience, won’t you come and have lunch on us and see if we can make things right.”

Alas there was nothing… not even a nasty reply. (Actually their first email address bounced so I had to find another which didn’t bounce, so I know they got it)

So obviously they didn’t care… My little email and my 50 friends didn’t count. Then, a few weeks later, I posted the email on my blog.

So now I am the 3rd result in Google for Nonna Lina.

A month goes by and a few days ago I get an email alerting me to a new comment on the story. It’s from the owner. I assume he Googled his restaurant’s name and got a little fright… but not enough of a fright to apologize… instead he writes a badly constructed list of excuses, demeaning my own ability to discern good food from bad food. Insists that their shocking food is true Italian Fare… the fact that 11 people found their food disgusting must mean that I run in very plebby social circles.

Then he strangely tells me that I should talk more… weird… I think what he’s trying to say is that we should have spoken to him then instead of writing about it on the internet… except, he forgets, we tried to talk to him but he wouldn’t listen and instead walked outside and started smoking.

Then, as if all of this wasn’t enough, he calls me a racist because I said that his waiter’s English was bad and we struggled to communicate with him. I must point out that his email had shocking English too. So now I’m a racist who doesn’t like Italian people… I must tell that to my Italian friends. Also, I’m constantly ripping off my girlfriend about her funny colloquialisms. Dammit, I must be a racist.

Actually, it had never occurred to me that his waiter was black until he brought it up.

Comments (1)