🦘 Jump into the repositories (git, mercurial…) of your filesystem with telescope.nvim, without any setup
Hi, it’s Clément! 👋
As a software engineer at Rothesay in London, I’m building fast tools in Python and Rust to make other developers more productive. Before that, at Paxos, I was building a smart order router for crypto markets in Rust. Before that, I was part of the DDoS protection team at Cloudflare, using technologies like eBPF or Rust. I presented some of my work at the Linux Plumbers Conference 2020. Previously, I worked on non-intrusive performance analysis at the SnT, a lab part of the University of Luxembourg. More on my CV.
In my spare time, I enjoy writing and contributing to open-source programs. I also blog mainly about performance and tools I use (like NeoVim, Hugo or SQLite). Some of my writing made it to the front page of HackerNews or Lobsters, sparking fruitful discussions in the comments. See the blog roll for my curated selection of blogs.
Selected Software Projects
Rusqlite Migration
↕️ Simple database schema migration library for rusqlite, written with performance in mind.
Readme in Static Site
💎 Transform and insert your GitHub readme in your static site.
Gohugo Asciinema
⏯️ Insert the Asciinema Player in your Hugo site with ease.
On the Blog
Link Aggregator Infrastructure
A look at the surprisingly simple infrastructure of link aggregators like HackerNews or Lobste.rs.
New Asciinema Hugo Module Versions
I’ve just added the last 8 versions of the Asciinema player to gohugo-asciinema, my Hugo module to easily integrate the Asciinema player to your website. Lots of exciting new features, like improved decoding and rendering efficiency as well as some support for streaming asciicasts. See the changelog links below for details of the changes. There were no changes made to the Hugo module itself, besides copying the JS & CSS from the Asciinema player....
My Commits and Tags Are Now Signed
Announcement I’m now signing my git commit and tags with an SSH key. Details of the fingerprint can be found in the security document. It says that commit after 2024-01-01 are going to be signed, because I’m starting now on one machine and I will propagate the configuration over the next few days to other machines. Why Why bother with cryptographic signatures? Anyone can pretend to be me. They just need to write my name and email in the author fields of a commit message....