Designing Code

Having started out as a designer and ended up in PHP coding, I thought I was an unusual breed. It turns out that's a path many took to PHP.  My reasons were simple when I was deciding which web technology to learn- I had a Mac. At the time (2001) Mac OSX had just come out, and, being based on Unix, PHP was the language to learn.

It was a good choice. PHP has matured and grown to be one of the top server-side languages on the web. I find a large percentage of job postings on the web are for PHP coders. The demand is outstripping the supply.

...I'm not complaining ; )

As a designer/coder, my skillset allows me to float between print layout, illustration, web design, coding and web application design/build- quite a broad spectrum. Having this ability, and lack of 90 hours in a day, I can get frustrated in what task to prioritize. Having a passion for both camps, I feel reluctant to give one up completely. I will always be a designer and I will always be a toolsmith- when I leave one for too long, I always want to go back to the other.

You are now looking at kevinbruce.com v4. I've had kevinbruce.com up and running since 2000 and it's running on the BCllc site engine that I created over the course of 5 years.

The BCllc site engine is built on PHP5 but is not OOP. I am currently planning out a complete rewrite in OOP based on frameworks I have yet to choose. ZEND, CakePHP, Symphony or CodeIgniter. I'm looking at all of these. If anyone has an opinion, I'd like to hear it!