Decisive

Gah, sometimes I swear I’m my own worst client.

On The Other Site (and I promise I’ll be letting it out into the wild soon – promise.) I’ve been working out how to get the necessary information into the bloody thing, and it was becoming more and more complex. Countries, Regions, Towns, and at least two other bits of information before we got to the crux of the matter, and so the page was hellish.

Mainly this was because I was trying to do it all in a way that makes sense for the long-term, and minimises the amount of data that’s repeated in the database. For instance, if you’ve got an address table, you don’t really want a buttload of records with the same town, county, and country – you’d want to have a “location” table that will hold those, so you can say in the address table “location=10”, and then in the location table, record ten has “town, county, country” in it. Makes sense.

Anyway, the way I’d done this was becoming incredibly complex, and so this morning I’ve been looking at it again, and figuring out better ways to do it. Well, by “better” I mean, of course, “simpler”- both from a coding point of view, and a usability one. All the same, it’s enough to make my head ache quite a lot.

The annoying bit is that I’d got it all to a point where it was actually pretty much working. It just took too long to get anything done, so the re-plan was necessary. And maybe when I develop things a bit more, I’ll come back to this way, and do it all with AJAX or something to make it nice to use. But I’m not convinced…