Coding for fun and spending your weekend indoors, more like.
One problem I have with coding for RPoL, besides the general fact I have no idea what I’m doing, is that I bite off more than I can chew. I had to abort a massive project I undertook for the site in about 2005 because it was too big. I know what I need to do, but the end of the tunnel is so far away there’s not even the glimmer of hope of some light shining down it. The more I work on the changes the more I realise needs to be done.
This all stems from opting not to use mySQL (or any structured database) back when I made RPoL in 2000. I opted for Berkeley databases, some of which are so basic they are actually flat text files, each record being a line in the file. The sad fact of all this is at the time I knew I should use SQL, but I looked at mySQL and could just not get my head around it (actually, it might have been to the fact that when I was originally learning programming they forced a lot of SQL onto us then and I hated it; I think it took over ten years to get over the trauma). Later in about 2004 when I revisited it, it all seemed so easy and I had no idea why I didn’t use them before. I’ve been slowly migrating the databases over to mySQL since.