Support up-and-coming indie game developers by playing their games. Leave a comment to tell them what you like or what can be improved.
Our tutorials go from basic Processing through advanced libGDX.
In my last dev log, I was trying to implement a local database creator, but I was stuck on a problem with Hibernate not connecting to the Derby database.
I've since figured that out thanks as always to StackOverflow: it turns out that between Derby 4.0.1 and 4.3.5,
(I also started watching West Wing, but that's neither here nor there.)
That took about a month of frustration and feeling like I wasn't getting anywhere, mostly because I wasn't. I absolutely love programming, so it's sometimes disheartening how much time is spent on boring setup stuff, which never seems quite documented enough. You'd think that we'd have most of the boring stuff out of the way, but it's never easy.
This is the circle of debugging: something wasn't working, so I changed a bunch of things, implemented a few example projects to test things out in, and in the end all I needed to change was a single property value. It feels like all that time was wasted and I'm right back where I started... like I just walked around in a circle.
Sometimes I'm jealous of people twenty years in the future, because surely by then it'll be trivial to do really exciting things. But then again, they'll probably be annoyed by their own futuristic setup problems.
But on the bright side, I think I have the setup part done, so now I'll be able to actually implement the darn thing. I know that probably nobody will use it, but the lack of a local database is a weird source of guilt for me, so getting it done will be a relief.
In other news, my freelancing job has continued. I've done a few small tasks, and I've started digging in to my first bigger debugging job. I'm pretty happy about the opportunity.
I'm going to resist the urge to excitedly list the stuff I'd like to do *after* the local database thing is done.