Blog

I created a way to deploy only tagged versions of my site to production using Vercel and the release-please bot. I used Vercel's ignored build step and a custom script to check for the presence of release-please commit messages. This ensures that only properly tagged versions are deployed to production.

Yes, once again I've fallen out of the habit of keeping things up to date here. I don't make New Year's resolutions but if I did it would be to try and keep this up to date a little more frequently. Mostly because I want to spend more time on hobby stuff this year (everyone loves a bit of CV-driven development).

We left off part 2 with code that worked and gave good results but was disastrously inefficient, taking minutes to finish the algorithms run on higher-resolution images. In this post, we're going to try and move some of the more computationally heavy code into WebAssembly to try and fix this issue.

Ok in part 1 we looked at finding dominant colours in an image, we got as far as showing the top 8 colours by pixel count, and showed that this isn't necessarily the best solution for real-world images as there are micro variations of colour within the image that aren't always immediately obvious to the naked eye.

During the interview for my current previous job, I was given a small pair-programming coding challenge to complete. Like all good coding challenges, it was probably beyond what could reasonably have been finished in an hour but it was fun and I got the job so my attempt couldn't have been too bad. Not finishing the challenge did annoy me though so here's my attempt at a more polished version of the challenge

This page is going to function as a test bed for the site's new styling, it's going to contain as many different markdown elements as possible in order to see whether or not we support them