… to WordPress?
Yep. I had written my blog from scratch, partially because I wanted to use it as a testing ground for various ideas and such. However, part of the problem of maintaining your own blog software is maintaining your own blog software. I think that I’ve pretty much milked the code for all it’s worth. So now I’ll stop maintaining my own code and start using someone else’s.
Yep. Let’s face it; the code base is a horrible stinking mess. The API is not intuitive in any way, shape or form. WordPress pretty much gets everything wrong…
… except that it gets the job done. Way too many programmers are way too proud of their code. Well, not really. They’re proud of their ability and they like any opportunity to talk about how great their abilities are. PHP was never about that (though we have our share of egotists). PHP was about getting the job done. Do I wish that the WordPress engine had a better architecture? Absolutely. Do I wish that the API was remotely intuitive? Yep. But the long and the short of it is that I don’t have the time to maintain the code base for a blogging application. So I use one that already exists, has plenty of templates available (I’m the world’s second worst designer) and has a large community around it.
So, yes, WordPress.