[australia] Why home grown CMS?

[Melanie Kendell]

On 10/10/06, Chris Blown <griffon at hinterlands.com.au> wrote:
> I have often noticed that programmers - if given a choice -  would
> prefer to code their own systems rather than learn an existing system
> well enough to extend and support it like their own code.

I have also come across the perception from some programmers that
building something in-house is somehow "free" because, after all, they
would be paid for being there anyway.

I think it also depends if the CMS implementation was something that
was seen as a project in its own right or something that evolved over
time as a side task. Back-door building of systems is easier than
back-door implementation of outside built systems (especially if you
go commercial and have to get a purchase order authorised).

My main concern with homegrown systems is that while its fun to build,
the programmer that is happy to maintain is rare, and one that will
document to a level where the system can be maintained once they have
become bored or moved on is rarer still.

-Melanie