updown.io

I've been using a simple trick on updown.io since May 2015 to make pages feel faster without doing much work.

In 2024, I migrated from UserVoice to Canny for user feedback collection.

Ruby 3.1.2 vs 3.3.5+YJIT in production In the previous article I discussed about my upgrade process from Ruby 3.1 to ruby 3.3, discovered a potential regression in a specific scenario, and ended up with synthetic benchmark results looking pretty great: Ba…

updown.io has been running on ruby 3.1 since... git log -p .ruby-version...

A lot of people are wondering about the technical stack used by updown.io and more generaly by one-man tech companies.

This investigation was surprising to me so I thought it would be interesting to share my findings and I hope you'll like it.

I wanted to improve the responsiveness of the Delete account action, which could be slow for bigger/older accounts due to the many associated records to be destroyed (downtimes, metrics) being sparsely distributed in the database.

For a while I've been thinking of "starting a tech blog".

Note: This article was initially published on Medium in 2019 and later moved to this official updown.io blog.

Note: This article was initially published on Medium in 2017 and later moved to this official updown.io blog.