In services with uptime, availability is often measured in the number of 9s, e.g. “4 9s” is 99.99% uptime. Whilst installed apps themselves don’t tend to have uptime in the same way, they do have another critically important metric: % of crash-free users! I’ve always heavily focused on this metric, so here’s some of the things I’ve picked up whilst chasing 100%.
Back in December, I got an email about something called the “Google Play Store Listing Certificate”. It seemed pretty relevant to my job, and I finally got round to completing it! It’s mostly targeted towards digital marketers, but it has value for engineers publishing on the store, so here’s a short unbiased review.
As mentioned a few weeks ago I’m now using the jekyll-anchor-headings scripts to add links to each header. This works great, but… unfortunately has side effects if the header is more than one line. Time to fix that!
I originally got into Android development by making a game in my spare time, Pixel Blacksmith. This game ended up becoming way more popular than I could have imagined, and persuaded me to follow app development as a career! Now, I’m open sourcing this and other game codebases.
Whilst Jekyll’s Minima theme is great, there’s a couple of very basic features I wish it had by default. I added the features myself today, and decided to start doing “release notes” style posts for the codebase used in both my blogs!
At work, we’ve had a bug that has appeared intermittently since before I joined. The navigation bar at the bottom of our app would very rarely become absolutely massive. For seemingly no reason. Today, I finally freed us from this menace!
On most larger software projects, at some point you’ll probably need to use a diagram on GitHub. Whether it’s explaining how components interact, a user’s flow, or project timelines, it’ll happen eventually, usually in a PR.
Waaaaay back in 2017, I experienced the most convincing phishing attack I’ve ever seen. I didn’t fall for it, but it was too close for comfort! I published my notes on Reddit and it got a lot of attention, and ended up in a few news articles.
When creating a new GitHub pages site with Cloudflare’s DNS, the default setting is proxying all data via Cloudflare. This is OK, but Cloudflare can slow down GitHub pages somewhat, and GitHub pages have no bandwidth limits so might as well serve directly.
Looking for non-software development posts? I've got another blog for those!