Archive for June, 2008


Monday, June 23rd, 2008

At the end of last week, my girlfriend and I moved to Seoul. I’m going to be working as a elementary level English teacher. I’m very excited about this and start my lessons this afternoon.

This city is amazing. Having lived in the countryside for the last few months, it’s great to be back in a city. I’ve always found the countryside solipsistically lonely and dull. Here, nobody stops. Ever. Not even at 5 am (I’m still on English time, what’s their secret?).


Monday, June 16th, 2008

When I first took a look at Ruby on Rails, my first thought was that all the code generation scripts were dangerous. It seemed like cut-and-paste programming on steroids. It also looked very useful and I put some code generation CLI scripts into Haddock CMS almost immediately. I quickly gave up on that as I confirmed my worst fears and realised that I was doing the most inflexible cut-n-paste style programming imaginable.

Over that last few days, I’ve been implementing a delta system for database structure in Haddock. It’s pretty rudimentary at the moment but it’s much better than the lack of a system that we had before. It uses SQLite for keeping track of which delta files have been applied to a particular instance of a Haddock project.

In order to write the CLI scripts to create, apply, list and reset the deltas system, I found it quicker to write a CLI script for creating new, blank CLI scripts. I figured that code generation CLI scripts are safe as long as they only generate 10 lines of code or fewer in a single class of a well defined type. Blank CLI script classes fit this description. Before long, however, I had started to write lots more CLI scripts to generate a lot more classes.

I’m not sure if this is going to save a lot of time or getting me to a bad place in terms of code maintenance really quickly. But for the time being, I like the new code generation scripts.

Check them out.

Haddock Sanity Check

Thursday, June 12th, 2008

I never set out to write a web framework. Haddock CMS has always been just the common elements of a lot of web sites that I’ve written and worked on. It’s taken a lot of time and effort but I think that investment will be returned in the long run. Hopefully 🙂

Part of the advantage of writing a framework by refactoring the elements to common to several sites is that it avoids over engineering features. Nothing in the framework should be there because it solves a general problem when a solution to a specific problem would have been better. That would go against doing the simplest thing that could possibly work.

However, I didn’t have a place where I could check that all of the plug-ins for Haddock CMS worked together. There now is one:

If you check out this to a vhost project root, it’s not a very useful site but a good place to check that everything is still working.