Blog

A look at the latest update to Storypoint Shuffle and the new features added in version 1.1.0

After 30 days of adding analytics to Storypoint Shuffle, I wanted to take a look at the data and get some insights into how people are using the app and if there were any key takeaways.

I recently moved my personal blog from Next.js to Astro as the framework to generate the site. In this post I'll share my experience with the transition, the benefits I've observed, and some challenges I encountered along the way.

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.

In this post I'm going to look at how to find the dominant colours in an image using JavaScript. This was a challenge I originally faced during a coding interview. I'll go over a simple JS implementation and some potential pitfalls to watch out for.

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