Please see this blog why the forums had been decommissioned.

Today I have decommissioned three of my web portals. The common factor? All three sites were forums using phpbb's PHP based free forum software. Why?

Because I got tired and pissed off having to constantly update the software due to security holes. Every couple of weeks I saw a red warning message in the version area of the software - informing me of YASH (Yet Another Software Hole).

Some people might believe that is a Good Thing - software automatically informing you about new updates. In general that is nice, however in this case I would have felt much better if there had been no holes - or at least more realistically a hole a year. Take OpenBSD - their clame to fame is

I had a huge problem. Since I am an avid photographer, I started building up a huge library of photos. I do not like archiving photos and delete them from my main library, since I like to have them all available for display.

The problem is that my library started pushing 200GB. It grows by about 100GB each year. I already have two 400GB HDD's in my G5 (RAID1), but with the OS and other applications I was running out of disk space. Since bigger hard drives are not readily available, I had to look for some form of external storage. I'll explain in this blog what my options were and why I dediced to build my own RAID array.

The easy way out would be to purchase a LaCie RAID system, but that would have put me back about R32,000. It can only provide 1.5TB of disk space (if using 500GB drives in RAID5). Furthermore, the speed is limited by the Firewire 800 interface (although fast, with large RAID5 arrays on SATA it is possible to go well over 100MB/s). Another option would have been the Apple XServe RAID. But that costs R60,000 for 750MB RAID5. Yeah it is massively scalable up to insane capacities, but it is just too expensive (and noisy). So I decided to look into building my own RAID array. Why? Because I already had a nice desktop Pentium 4 3.2GHz machine with 2GiB RAM. Since the case can only handle 4 hard drives, and ventilation sucked I decided to replace it too. Fortunately my power supply is rated at 500W - keeping many hard drives spinning requires lots of power.

As any serious amateur photographer or professional for that matter should know by now, Apple released their professional Photography Workflow and RAW Processing software late November last year. It is called Aperture and I do not recall any other photographical software product causing so much uproar in the community. Here is my take on it all...

First some background. Apple always had very strong marketing techniques and when they marketed Aperture whilst it was still on back-order it was no exception. They had the most beautiful video clips of the application in action - enough to have anyone drool for this application. It looked slick, and seemed to fill the missing gap between the camera and the output media.

Apple marketed it as a RAW Workflow system with Professional Project Management, Nondestructive Image Processing and Versatile Printing and Publishing.

I was recently involved in a project where I was reminded of a typical scenario in today's IT environments that still baffles me...

There are many different schools of thought when it comes to how and when to apply code optimisations. Some people would have you believe code should be optimised from the start. Others believe in getting it functional first, then optimising.

This blog is not about how to apply optimisations and the bigger paradigm of when and how to most effectively incorporate it in to a project. It is rather about that scenario where code is functional, now you are looking at ways to improve the performance.