2025 is off to a pretty good start! I spent 3 days alone in Phu Quoc to recharge, didn’t do anything except swimming and reading Thistlefoot while drinking coconuts. I used to go regularly when I was single, but now it’s going to be my last trip for a while. Got lucky with the weather as well! Back home, I’ve made some progress on my crossword solver app. I opened a WebSocket to stream the intermediary results (“dead ends”) as the backtracking algorithm progresses; I think it looks cool. In the frontend, I’ve added a history so you can Ctrl-Z, and other minor convenience changes (right-click to toggle between black and white cells, etc). I should define the scope, though; I don’t plan to make it a full-blown “crossword editor.” I think I will just add the ability to export a grid and be done with it. ...

Looking back, 2024 was a pretty good year across all metrics! Learned new things at work even though it’s my 5th year at the job, been pretty healthy and fit, not been drinking much (was a dry NYE, and will be doing a dry January). So I’m not taking any big resolutions for this year; it should be plenty busy already with the birth of my second kid in a few months. I’ll just try to finish and release my crossword generator application before that, and that will be it. Maybe try to be more smiley and relaxed in general. ...

Since the release of ChatGPT more than 2 years ago, I have felt a strong disconnect with the opinions on HackerNews about AI. It really feels like an Anti-AI (especially anti-OpenAI) echo chamber, neverendingly predicting the advent of AI winters, always repeating the same arguments (usually some flavor of “it’s not intelligent”, “what is AGI?”, “how can you trust it?”). Well, given that the generated code compiles, the tests pass and the program works as expected, I’m not sure what there is to complain about. I feel that HN is about as wrong about AI as it was about cryptocurrencies. Eventually, I mostly stopped reading the comments, I just use it as a link aggregator now. ...

I took a day off on this Christmas day, and I got inspired to revive this blog by reading Simon Willison’s “approach to running a link blog”. I like his blog to keep updated about the new models’ capabilities and developments in the AI world in general. He makes small experiments to put the models into practice, with a good dose of enthusiasm, and I want to follow a similar approach for this blog: sharing interesting articles I read, and some of my daily programming experiments, while “trying to add something extra”. ...

In this post, we’ll discuss various common ways of handling API rate limits, and I’ll introduce a new tool I’ve been working on called MeterFlow. Most APIs have rate limits, usually counted in requests per minute, but other resources can be limited as well (for instance, the number of characters you can translate with the Google Translate API, or the number of tokens you can generate with some LLM API). When you exceed the rate limit, the API will return a 429 status code, telling you to slow down. There are various ways of dealing with API rate limits in your code. ...