bit mill software

This post is a continuation of a tour of CMS (Content Managment Systems) I've known and loved,

Drupal was the runner-up contender in my PHP-based CMS research. I used it to quickly build my website--not particularly pretty, but but it works for what I need.

So in a prior post, I brought up the subject of Content Management Systems. I thought I'd go through some of the CMSes I've run across so far.

So there I was...I needed my own website. As is often the case, I was busy enough from the start that I didn't really have a need for a website initially.

I'm a software developer which means that I love to create programs and websites...from scratch. Need a web application with some dynamic pages, and moving parts? No problem, I can code it up for you from scratch--all it takes is a lot of time and that means a lot of expense. As a budding entrepreneur wrestling with the tradeoff of effort vs. reward, when it came time for me to set up a website, I went with a CMS--a Content Management System.

After seventeen years working in corporate IT as a staffer, contractor & consultant, I decided to go rogue and hang out my own shingle. As part of the shift from enterprise IT to small and medium business IT, I have also changed focus from Java & Oracle to the standard open-source technology stack that is behind the majority of websites: Linux - Apache - MySql - PHP (LAMP).

These technologies are production ready and rock-solid. An added benefit is that developers can frequently get more done faster with a scripting language like PHP.