Optimising – Harder, Better, Faster, Stronger

Well hello there, reader. It’s time to talk about optimisation – the process of realising that what you did the first time was terrible and finding a new way that runs a hundred times better. Fortunately, in the particular example I’m about to go through, I’m not optimising my own code, but a program provided to me.

This idea behind this program is that it renders an image of various 3D shapes by using a series of ray traces. For each and every pixel in the window, the program performs a ray trace that returns the colour of that particular pixel, one by one. Considering there are a few thousand pixels involved, this takes a while. By default, the original took 80.157 seconds to render the entire image on my machine. That’s my time to beat.



Poorly ADAPTed

So a couple of weeks ago I began working on a project of mine named ADAPT. And then I stopped. Pretty much immediately. I work for a day and didn’t touch it for a fortnight because holidays. However, as of yesterday, development has officially resumed (despite never having officially stopped). So, a brief progress report on where it is at the moment.

ADAPT is currently at Version It features a title that displays the current month and a button that allows you to create a new task. Whilst you can currently enter all the task data, I have yet to code any method of storing and using that data. So really, all you do is press two different buttons to alternate between two different windows. Not that exciting, but it’s getting there. Slowly. Given that I have no experience with this program, it’s going to take some time for me to get a feel with it and work out what the hell is going on, so bear with me. Anyway, that’s just about everything there is to say on the matter. Hopefully I’ll have more ADAPT updates for you soon.